MCP Server Endpoints
myweave provides multiple endpoints for AI integration:| Endpoint | Purpose | Use Case |
|---|---|---|
https://docs.myweave.ai/llms.txt | AI Sitemap | Index of all documentation pages for AI crawlers |
https://docs.myweave.ai/mcp | MCP Server | Real-time documentation queries and API execution |
Available MCP Tools
When you connect to myweave’s MCP server, your AI can execute this tool:| Tool Name | API Endpoint | What It Does |
|---|---|---|
chat | POST /chat | Start or continue conversations |
These tools are defined in our OpenAPI specification and automatically exposed through the MCP server.
Your AI can execute them directly when you ask questions or give commands.
Example Tool Usage
Ask your AI to execute tools:The AI automatically maps your natural language requests to the appropriate MCP tool,
constructs the correct API call, handles authentication, and returns the results.
Claude Desktop Setup
Step 1: Locate Configuration File
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Step 2: Add myweave MCP Server
Edit the file and add:When Claude executes a myweave API call, it will prompt you for a JWT (Bearer token) per our OpenAPI security. The AI agent handles attaching it.
Step 3: Restart Claude Desktop
Close and reopen Claude Desktop for changes to take effect.Step 4: Test the Integration
Ask Claude:Example Prompts
Generate Integration Code:Cursor IDE Setup
Step 1: Install MCP Extension
In Cursor, install the MCP extension for Model Context Protocol support.Step 2: Configure MCP Server
Create or edit.cursor/mcp.json in your project:
When Cursor executes a myweave API call, it will prompt you for a JWT based on the OpenAPI security requirements. The AI handles authentication internally.
Step 3: Restart Cursor
Step 4: Use in Development
Now when coding, Cursor can:- Query myweave docs automatically
- Generate integration code
- Provide accurate API examples
- Reference latest endpoint specifications
Example Usage in Cursor
While coding:Custom MCP Client
Build Your Own MCP Client
Step 1: Install MCP SDKYour MCP client will automatically prompt for the required JWT (Authorization: Bearer) when executing API calls.
- MCP client reads that
/chatrequires Bearer auth (from OpenAPI spec) - Prompts user for a JWT (or uses cached credential)
- Automatically includes
Authorization: Bearer tokenin requests
Direct llms.txt Integration
For simpler integrations without full MCP protocol:Load Documentation Index
Load Complete Documentation
Authentication
What You Need
myweave API requires authentication for all API requests:- API Key - Required header:
X-API-Key - JWT Token - Optional header:
Authorization: Bearer(for user-specific requests)
How It Works
When your AI agent tries to execute a myweave API call through MCP:- AI reads OpenAPI spec → Sees that
X-API-Keyheader is required - AI prompts you → “Please provide your myweave API key”
- You provide the key → AI stores it securely for the session
- AI executes API call → Includes
X-API-Key: your_keyheader automatically - Request goes to myweave → Your API authenticates and processes the request
Your API key is handled by your AI tool (Claude, Cursor, etc.) and sent directly to
myweave’s API. The MCP server just serves the documentation—authentication happens
between the AI agent and myweave API.
For complete details on authentication methods, JWT tokens, login flows, and token refresh,
see the Authentication Guide.
Verification
After configuring MCP, test that it’s working: Test 1: Documentation QueryTroubleshooting
MCP server not responding
MCP server not responding
Symptoms:
- AI says it can’t access myweave documentation
- No response when asking about myweave
-
Check Configuration File Path
- Ensure you edited the correct config file
- Verify JSON syntax is valid (no trailing commas, proper quotes)
-
Restart Your AI Application
- Close and completely restart Claude Desktop or Cursor
- Some changes require a full restart
-
Test Manually
Should return documentation index.
-
Check Network Connection
- Ensure you have internet access
- Check if firewall is blocking the connection
Authentication errors when executing API calls
Authentication errors when executing API calls
Symptoms:
- “401 Unauthorized” errors
- “Missing or invalid API key”
- API calls fail but doc queries work
-
Provide API Key When Prompted
- When your AI asks for API key, provide it
- The AI will store it securely for the session
-
Verify API Key is Valid
Test your API key manually:
- Request New API Key If your key is invalid, request a new one from [email protected]
-
Check for Typos
- Ensure you copied the full API key
- No extra spaces or line breaks
- API keys start with specific prefixes (check your key format)
JWT token expired
JWT token expired
Symptoms:
- “Token expired” errors
- User-specific requests failing
- Works initially, then stops after ~1 hour
- Refresh Your JWT Token See the Authentication Guide for token refresh flow
- Provide New Token to AI When prompted, provide the refreshed JWT token
- For Long Sessions Implement automatic token refresh in your application. See Authentication Guide.
AI not finding myweave documentation
AI not finding myweave documentation
Symptoms:
- AI says “I don’t have information about myweave”
- Queries return generic responses instead of specific docs
- Use Explicit References Try: “Using the myweave MCP server, show me how to start a chat”
-
Verify MCP Server Name
- Check that server name in config matches what you reference
- Try: “Using @myweave, show me the API endpoints”
-
Check MCP is Actually Configured
- Ensure config file has
mcpServerssection - Verify no JSON syntax errors
- Ensure config file has
- Test with Simple Query Try: “List all available MCP servers” Should show “myweave” if configured correctly
Can't execute API calls (only doc queries work)
Can't execute API calls (only doc queries work)
Why This Happens:
- Some MCP clients only support documentation queries
- API execution requires additional permissions
- API key may not be properly configured
-
Verify API Execution is Supported
- Claude Desktop: ✅ Supports API execution
- Cursor: ⚠️ May be documentation-only (check version)
- Custom clients: ✅ Depends on implementation
- Provide API Key When Prompted Ensure you provide the correct API key when the AI tool asks for it.
- Use Custom Client for Full Control Build your own MCP client for complete API execution support. See Examples for complete implementations.
Next Steps
Use Cases
See real-world examples of hybrid AI apps
Code Examples
Complete implementations for TypeScript, Python, React
Chat API
Explore all API endpoints
Authentication
Learn about API keys and JWT tokens
Get API Access
Ready to build AI apps that integrate human expertise?Request API Key
Email [email protected] to get your API key and start building

