api-v1-docs — Motomarks MCP Server MCP Resource

api-v1-docs is one of 2 resources on the Motomarks MCP Server MCP server. Connect the server and your client can attach it as context.

by client

How to attach api-v1-docs from your client

• Claude Code Motomarks MCP Server Resource/api-v1-docs run in your project directory
• Claude Desktop Motomarks MCP Server Resource/api-v1-docs ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Motomarks MCP Server Resource/api-v1-docs ~/.cursor/mcp.json
• VS Code Motomarks MCP Server Resource/api-v1-docs .vscode/mcp.json
• Zed Motomarks MCP Server Resource/api-v1-docs ~/.config/zed/settings.json
• Windsurf Motomarks MCP Server Resource/api-v1-docs ~/.codeium/windsurf/mcp_config.json
• Cline Motomarks MCP Server Resource/api-v1-docs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Motomarks MCP Server Resource/api-v1-docs ~/.gemini/settings.json
• Grok Motomarks MCP Server Resource/api-v1-docs .mcp.json (in your project root)
• ChatGPT Motomarks MCP Server Resource/api-v1-docs Settings → Connectors → Advanced → Developer mode
• Claude.ai Motomarks MCP Server Resource/api-v1-docs Settings → Connectors → Add custom connector
• LangChain Motomarks MCP Server Resource/api-v1-docs pip install langchain-mcp-adapters

Other resources on this server

• image-cdn-docs

Motomarks MCP Server also offers 3 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.