get_maker_marks — Marks & Signatures MCP Tool Read-only
get_maker_marks
(get maker marks) is one of 5 tools on the
Marks & Signatures
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_maker_marks from your client
- Claude Code Marks & Signatures get_maker_marks run in your project directory
- Claude Desktop Marks & Signatures get_maker_marks ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Marks & Signatures get_maker_marks ~/.cursor/mcp.json
- VS Code Marks & Signatures get_maker_marks .vscode/mcp.json
- Zed Marks & Signatures get_maker_marks ~/.config/zed/settings.json
- Windsurf Marks & Signatures get_maker_marks ~/.codeium/windsurf/mcp_config.json
- Cline Marks & Signatures get_maker_marks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Marks & Signatures get_maker_marks ~/.gemini/settings.json
- Grok Marks & Signatures get_maker_marks .mcp.json (in your project root)
- ChatGPT Marks & Signatures get_maker_marks Settings → Connectors → Advanced → Developer mode
- Claude.ai Marks & Signatures get_maker_marks Settings → Connectors → Add custom connector
- LangChain Marks & Signatures get_maker_marks pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marksandsignatures-com https://marksandsignatures.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 6 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.