Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.shingleai.com/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through connecting the ShingleAI MCP server to Cursor IDE, allowing Cursor’s AI to access your contacts, messages, and other business data while coding.

​
Prerequisites

Before you begin, ensure you have:

​
Connect

Cursor supports streamable-HTTP MCP servers and runs the OAuth 2.1 + PKCE handshake for you.
  1. Add ShingleAI to your Cursor MCP config. Use .cursor/mcp.json in a project directory, or ~/.cursor/mcp.json for every project: 
    {
    "mcpServers": {
        "shingleai": {
            "url": "https://mcp.shingleai.com/mcp"
        }
    }
}
    You can also add the server through File → Preferences → Cursor Settings → MCP, which writes the same JSON.
  2. Restart Cursor.
  3. The first time Cursor calls a ShingleAI tool — or when you click Connect in the MCP settings — Cursor opens a browser tab for OAuth.
  4. Sign in to ShingleAI and approve the consent screen. Cursor stores the access token and the tools become available in chat.
See Authentication for details on the OAuth handshake.

​
Verification

To verify the connection is working:
  1. Open Cursor’s AI chat (Cmd+L or Ctrl+L)
  2. Ask: “What ShingleAI tools do you have access to?”
  3. Cursor should list the available tools

​
Example Usage

Once connected, you can use ShingleAI tools in your development workflow:
TaskExample Prompt
Find contact info”Look up the contact details for our main client”
Search communications”Find all messages about the API integration”
Review history”Show the conversation history with the design team”

​
Troubleshooting

Possible causes:
  • Configuration file in wrong location
  • Invalid JSON syntax
  • Cursor not restarted
Solutions:
  1. Verify the configuration file path
  2. Validate your JSON syntax
  3. Completely restart Cursor (not just reload window)
If the OAuth browser tab fails to load, check that you can reach https://mcp.shingleai.com/.well-known/oauth-protected-resource from your machine.If Cursor shows a stale token error, remove the shingleai entry from your mcp.json, restart Cursor, and re-add it — that forces a fresh Dynamic Client Registration.See Authentication for the underlying flow.
Cursor currently supports MCP tools but not MCP resources. This means you can call ShingleAI tools (like createContact, listMessages) but cannot access read-only MCP resources that some servers provide.

​
Next Steps

Available Tools

Explore all available MCP tools

Authentication

Learn about MCP server authentication
Last modified on May 2, 2026