Integrations & API

Sponsy MCP

Connect Claude, ChatGPT, Codex, and Cursor to Sponsy with the hosted MCP server and your Sponsy account.

Sponsy MCP is a closed beta integration for connecting AI tools to Sponsy through the Model Context Protocol. Use it when an approved AI client needs structured access to Sponsy data and workflows.

The canonical MCP surface is hosted by Sponsy. The older standalone sponsy-mcp package is deprecated and should only be treated as historical reference.

Closed beta access: Sponsy MCP is not open for every workspace yet. If you want MCP access or need approved access to private Sponsy data through an AI client, contact Sponsy and we can review the right setup for your workspace.

Access

Sponsy MCP is currently available by request. Contact Sponsy support if you want access enabled for your workspace.

Once access is enabled, connect using the client instructions below. Sign in with your Sponsy account, choose your workspace, and approve the requested permissions.

Starter includes read-only MCP access. Pro and Custom also allow write actions, subject to your permissions and the enabled beta capabilities. All plans still need beta access before connecting.

Permissions

MCP access is permissioned. Only grant access to AI clients and users that should be able to inspect or act on Sponsy workspace data.

Review token and OAuth client access regularly, and revoke clients that are no longer in use.

What MCP can be used for

Depending on the enabled beta capabilities, MCP can help AI clients:

List and inspect publications.
Search customers.
Retrieve slot details.
Review inventory context.
Work with Sponsy data in tools such as Claude Desktop, Cursor, or other MCP-compatible clients.

Setup checklist

Request beta access for your workspace.
Add Sponsy's hosted server to your AI tool:
- Name: sponsy
- Server URL: https://mcp.getsponsy.com/mcp
- Transport: Streamable HTTP (called http in some clients)
- Authentication: OAuth
Complete the browser sign-in and choose the Sponsy workspace you want to use.
Test with a read-only request: "Use Sponsy to list my publications."

Sponsy supports automatic OAuth client registration. You do not need to copy an API key or access token into the configurations below. If your client asks you to choose between a published OAuth identity and automatic registration, choose automatic registration (DCR).

Client instructions last checked against official documentation on October 4, 2026. Menu names and availability can vary by client version, plan, and workspace policy.

Connecting Claude

Claude, Claude Desktop, and Cowork

Custom remote connectors are available on Free, Pro, Max, Team, and Enterprise plans. Free accounts can add one custom connector. On Team and Enterprise, an owner or someone with the required connector-management permission must add Sponsy for the organization first.

Open Customize → Connectors, then + Add → Add custom connector. For an organization, open Organization settings → Connectors → Add → Custom → Web.
Name the connector Sponsy, enter https://mcp.getsponsy.com/mcp, and click Continue.
Review the detected OAuth settings. Choose Sign in now and Register automatically under OAuth client, then click Add.
Sign in to Sponsy and choose your workspace. Organization members open Customize → Connectors → Sponsy → Connect to sign in individually.
In a chat, open + → Connectors and enable Sponsy.

See Claude's official custom connector guide.

Claude Code

Add the remote server for your user account:

claude mcp add --transport http --scope user sponsy https://mcp.getsponsy.com/mcp

Start Claude Code, enter /mcp, select Sponsy, and authenticate in your browser. Current versions also support claude mcp login sponsy from the terminal. After signing in, try the read-only request from the setup checklist.

See Claude Code's official MCP guide.

Connecting ChatGPT

Use ChatGPT on the web with developer mode. OpenAI documents access for Plus, Pro, Business, Enterprise, and Edu accounts; managed workspaces also apply admin permissions and rollout rules.

Open Settings → Security and login and enable Developer mode. If your workspace uses the Apps interface, look under Settings → Apps → Advanced settings. Ask your workspace admin if the option is unavailable.
Open Plugins, select +, and create a developer-mode app. In the Apps interface, use Apps → Create in user or workspace settings.
Name it Sponsy, enter https://mcp.getsponsy.com/mcp, and choose OAuth. Use automatic registration (DCR) if a registration choice is shown; leave optional client ID and secret fields empty.
Complete Sponsy's sign-in and workspace selection. If shown, click Scan Tools, wait for discovery, then click Create.
Start a chat and select Sponsy from the + or developer-mode tools menu. Try the read-only request above.

See OpenAI's developer mode guide and workspace setup and permissions.

Connecting Codex

Desktop settings

Open Settings → MCP servers → Add server in the desktop app.
Name the server sponsy, choose Streamable HTTP, and enter https://mcp.getsponsy.com/mcp.
Save, select Restart, then Authenticate when the server requests sign-in.
Sign in to Sponsy, select your workspace, and use /mcp in the composer to check the connection.

CLI and IDE extension

Run these commands in your terminal:

codex mcp add sponsy --url https://mcp.getsponsy.com/mcp
codex mcp login sponsy

Finish the browser sign-in, then start a new session. The desktop app, CLI, and IDE extension share ~/.codex/config.toml on the same host. If you prefer to edit that file, add:

[mcp_servers.sponsy]
url = "https://mcp.getsponsy.com/mcp"

Then run codex mcp login sponsy. Use codex mcp list to check the saved server and /mcp in a session to view its connection.

See OpenAI's official Codex MCP guide.

Connecting Cursor

Add Sponsy to ~/.cursor/mcp.json for all projects, or .cursor/mcp.json in one project. If the file already contains servers, add the sponsy entry inside its existing mcpServers object.

{
  "mcpServers": {
    "sponsy": {
      "url": "https://mcp.getsponsy.com/mcp"
    }
  }
}

Save the file, open Cursor's Customize page, and find Sponsy in the MCP server list. Enable it and complete the OAuth sign-in when prompted. If your version shows Needs login, select it to open the browser. Choose your Sponsy workspace, then use Agent chat to try the read-only request above. If the server does not appear, restart Cursor. Your team may restrict which MCP servers you can use.

See Cursor's official MCP guide.

Keeping your connection active

Sponsy issues a short-lived access token and, when offline_access is granted, a refresh token so your client can renew access without another browser sign-in. Let the client store and renew these credentials through its normal OAuth flow.

Troubleshooting

If the MCP client cannot connect, verify that the workspace has beta access, the token or OAuth client is still active, and the AI tool is using the current Sponsy-hosted MCP endpoint.

If a tool can connect but cannot access expected data, check the workspace context and permissions assigned to the MCP token or client.

If you connected Sponsy but the assistant does not use its tools, enable Sponsy for the current chat and explicitly ask it to "use Sponsy." In Cursor, use Agent chat. In ChatGPT, check that the app is selected for the conversation.

If sign-in fails during client registration, check that the client is using automatic registration (DCR). Sponsy's endpoint currently supports DCR rather than published client identity documents. Do not switch to No authentication to bypass a sign-in error.

If Codex repeatedly asks you to sign in, restart it and authenticate the existing Sponsy server once through its MCP settings or codex mcp login sponsy. If the prompts continue, send Sponsy support your Codex version, whether you use the desktop app, CLI, or IDE extension, and the approximate time of the failed connection. Share the error text, but leave out access tokens, refresh tokens, and authorization codes.