Cursor supports MCP servers, letting you use Toolcog directly in your IDE for API operations while coding.
Cursor uses JSON configuration files for MCP servers. Choose based on your needs:
| Location | Scope |
|---|---|
~/.cursor/mcp.json | All projects (user-level) |
.cursor/mcp.json | Single project |
Create or edit ~/.cursor/mcp.json:
{ "mcpServers": { "toolcog": { "url": "https://mcp.toolcog.com" } }}Create .cursor/mcp.json in your project root:
{ "mcpServers": { "toolcog": { "url": "https://mcp.toolcog.com/mycompany/project-catalog" } }}You can also add MCP servers through the Cursor UI:
https://mcp.toolcog.comAfter configuration, Toolcog’s tools are available in Cursor’s AI features. Ask Cursor:
“Find the Stripe API operation for creating a payment intent”
Cursor will use Toolcog to discover the operation, show you its interface, and help you use it in your code.
When Cursor needs to access your Toolcog account:
For downstream services (GitHub, Stripe, etc.), the same flow applies when you try to call an operation that requires authorization.
Connect to specific catalogs by using scoped URLs:
{ "mcpServers": { "toolcog-internal": { "url": "https://mcp.toolcog.com/mycompany/internal-apis" }, "toolcog-public": { "url": "https://mcp.toolcog.com" } }}In Cursor, ask the AI:
“What operations does Toolcog have available for Stripe?”
If you see a list of Stripe operations, Toolcog is connected.