Sponsy MCP
Connect AI tools to Sponsy through the Sponsy MCP beta so approved clients can inspect and work with Sponsy data.
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, manage MCP access from the API or integration settings area in Sponsy. Access may include a token, OAuth client setup, or workspace-specific authorization depending on your beta configuration.
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.
- Confirm the MCP endpoint and authentication method with Sponsy.
- Create or authorize the MCP client in Sponsy.
- Add the MCP server configuration to your AI tool.
- Test with a read-only request, such as listing publications or searching for a customer.
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.