Quickstart

This guide gets an MCP client talking to Shanone end to end: API key → client config → first OAuth connection → first tool call.

Prerequisites

A Shanone account at app.shanone.ai
One of: Cursor, Claude Code, or any other MCP client that supports either stdio servers or remote Streamable HTTP servers with custom headers
Node.js 18+ if you’re using the local stdio proxy (recommended path below)

Step 1: Get an API key

Open API Keys

Create a key

Click Create API Key, give it a descriptive name (e.g. “Cursor — laptop”), and choose an expiration before confirming. The default is 30 days; you can also choose 7, 60, or 90 days, Custom (1–366 days), or Never. See Expiration for details.

Copy it now

The plaintext key is shown once, in the form sh_xxxxxxxxxxxxxxxx. Copy it somewhere safe — Shanone only stores a hash of it afterward.

Treat your API key like a password. Anyone with it can call every tool your account has permission to run. Don’t commit it to version control.

Step 2: Add Shanone to your MCP client

The simplest way to connect is the local stdio proxy, @duzzle/shanone-mcp, which runs on your machine and forwards MCP tool calls to Shanone’s API over HTTPS using your API key.

Cursor
Claude Code
Any MCP client (direct HTTP)

Add this to ~/.cursor/mcp.json (or Cursor Settings → MCP):

{
  "mcpServers": {
    "shanone": {
      "command": "npx",
      "args": ["-y", "@duzzle/shanone-mcp"],
      "env": {
        "SHANONE_API_KEY": "sh_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

Restart Cursor (or reload the MCP server list) to pick it up.

claude mcp add shanone \
  --env SHANONE_API_KEY=sh_xxxxxxxxxxxxxxxx \
  -- npx -y @duzzle/shanone-mcp

Or add it to .mcp.json in your project:

{
  "mcpServers": {
    "shanone": {
      "command": "npx",
      "args": ["-y", "@duzzle/shanone-mcp"],
      "env": {
        "SHANONE_API_KEY": "sh_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

If your client speaks remote Streamable HTTP MCP and can send custom headers, you can skip the local proxy entirely and point it at Shanone’s hosted endpoint:

{
  "mcpServers": {
    "shanone": {
      "url": "https://app.shanone.ai/mcp",
      "headers": {
        "Authorization": "Bearer sh_xxxxxxxxxxxxxxxx",
        "X-Org-Id": "org_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

The direct endpoint requires both your API key and your organization ID (also visible on the API Keys page) — this composite check means a leaked API key alone isn’t enough to call your tools. See MCP Setup for the full comparison between this and the local proxy.

Step 3: Connect your first integration

Shanone doesn’t ask you to pre-authorize every service up front — tools that need OAuth simply return a connect_link the first time your agent tries to use them.

Ask your agent to do something that needs a service

For example, in Cursor’s chat: “Post ‘hello from Shanone’ to the #general channel on Slack.”

Follow the connect link

If Slack isn’t connected yet, the tool call returns a message like Authentication Required with a connect_link. Open it in your browser and complete the OAuth flow.

Retry the same request

Ask your agent to try again. This time the call succeeds because Shanone now has a valid, stored OAuth token for that service and user.

You can also connect integrations proactively from Integrations in the Shanone dashboard, without waiting for an agent to hit an auth wall.

Step 4: Run your first tool call

Try a few natural prompts and watch your agent work through the meta-tool workflow:

"What Shanone tools are available for GitHub?"
"Search Shanone for tools related to creating a Notion page"
"Create a GitHub issue titled 'Fix login redirect bug' in my-org/my-repo"

Under the hood, your agent is calling shanone_search_tools (or shanone_list_service_tools for a full listing), then shanone_execute_tool with the arguments it worked out — no manual JSON required from you.

What’s next

MCP Overview

Understand the full meta-tool workflow, Skill Vendor, and Permission Vendor tools

Best Practices

Get better results by phrasing agent instructions well

Integrations

Browse what’s available for Slack, GitHub, Notion, Stripe, and more

Save a Skill

Turn a workflow you just did into a reusable Skill

Getting Started

How to Use Shanone

Product Guide

Release Notes

Prerequisites

Step 1: Get an API key

Step 2: Add Shanone to your MCP client

Step 3: Connect your first integration

Step 4: Run your first tool call

What’s next

MCP Overview

Best Practices

Integrations

Save a Skill

​Prerequisites

​Step 1: Get an API key

​Step 2: Add Shanone to your MCP client

​Step 3: Connect your first integration

​Step 4: Run your first tool call

​What’s next

MCP Overview

Best Practices

Integrations

Save a Skill

Prerequisites

Step 1: Get an API key

Step 2: Add Shanone to your MCP client

Step 3: Connect your first integration

Step 4: Run your first tool call

What’s next