Service manifest — mastering MCP Resource
Service manifest
is one of 4 resources on the
mastering
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Service manifest from your client
- Claude Code mastering Resource/Service manifest run in your project directory
- Claude Desktop mastering Resource/Service manifest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mastering Resource/Service manifest ~/.cursor/mcp.json
- VS Code mastering Resource/Service manifest .vscode/mcp.json
- Zed mastering Resource/Service manifest ~/.config/zed/settings.json
- Windsurf mastering Resource/Service manifest ~/.codeium/windsurf/mcp_config.json
- Cline mastering Resource/Service manifest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mastering Resource/Service manifest ~/.gemini/settings.json
- Grok mastering Resource/Service manifest .mcp.json (in your project root)
- ChatGPT mastering Resource/Service manifest Settings → Connectors → Advanced → Developer mode
- Claude.ai mastering Resource/Service manifest Settings → Connectors → Add custom connector
- LangChain mastering Resource/Service manifest pip install langchain-mcp-adapters
Other resources on this server
mastering also offers 2 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 14 November 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.