Connect your client

Add the Signa MCP server to any AI client in one step

Signa is a remote MCP server over Streamable HTTP. There’s nothing to install — point your client at one URL and authenticate:

https://api.signa.so/mcp

OAuth is recommended. Most clients open a browser for you to sign in at app.signa.so on first use, then refresh the token silently — no key to paste or rotate. Prefer an API key for scripts or headless setups; see Authentication & security.

Prerequisites

• A Signa account with an organization — sign up
• An MCP-capable client (Claude, ChatGPT, Cursor, VS Code, …)

Add the server

Claude Code

One command, OAuth login on first use:

claude mcp add --transport http signa https://api.signa.so/mcp

To use an API key instead of OAuth:

claude mcp add --transport http signa https://api.signa.so/mcp \
  --header "Authorization: Bearer sig_YOUR_KEY"

Run /mcp inside Claude Code to check the connection and authenticate.

Claude Desktop & Claude.ai

Add Signa as a custom connector:

1. Open Settings → Connectors → Add custom connector
2. Name it Signa and enter the URL https://api.signa.so/mcp
3. Save, then click Connect and complete the browser login

Prefer editing the config file? Add this to claude_desktop_config.json and restart Claude Desktop:

{
  "mcpServers": {
    "signa": {
      "url": "https://api.signa.so/mcp",
      "type": "streamableHttp"
    }
  }
}

macOS

~/Library/Application Support/Claude/claude_desktop_config.json

Windows

%APPDATA%\Claude\claude_desktop_config.json

Cursor

Add to .cursor/mcp.json (project) or your global Cursor MCP settings:

{
  "mcpServers": {
    "signa": {
      "url": "https://api.signa.so/mcp"
    }
  }
}

Cursor discovers the OAuth flow automatically. You should see signa appear under MCP Tools with a green status once connected.

ChatGPT

Requires a ChatGPT plan with MCP connectors enabled.

1. Go to Settings → Connectors → Create (enable Developer mode if needed)
2. Enter the URL https://api.signa.so/mcp
3. Choose OAuth for authentication and complete the login at app.signa.so

Gemini CLI

Add Signa as a remote HTTP MCP server:

{
  "mcpServers": {
    "signa": {
      "httpUrl": "https://api.signa.so/mcp"
    }
  }
}

If your Gemini surface does not run an interactive OAuth flow, create a Signa API key and configure it as a bearer token header instead.

VS Code

Add to .vscode/mcp.json, or run MCP: Add Server from the Command Palette:

{
  "servers": {
    "signa": {
      "type": "http",
      "url": "https://api.signa.so/mcp"
    }
  }
}

Windsurf

Add to your Windsurf MCP config (note the serverUrl key):

{
  "mcpServers": {
    "signa": {
      "serverUrl": "https://api.signa.so/mcp"
    }
  }
}

Other clients

Any client that supports Streamable HTTP can connect directly to:

https://api.signa.so/mcp

The client discovers the OAuth authorization server via the /.well-known/oauth-protected-resource endpoint and guides you through login.

For API or enterprise products that do not support interactive OAuth, use a static Signa API key as Authorization: Bearer sig_YOUR_KEY.

Stdio-only client? Bridge it with mcp-remote:

{
  "mcpServers": {
    "signa": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.signa.so/mcp"]
    }
  }
}

Verify the connection

Ask your agent:

“Use Signa to search for NIKE trademarks in the US.”

You should see it call the search_trademarks tool and return live USPTO results. If it doesn’t, see the authentication troubleshooting section.