vela.magazine.sequence_path — corpus MCP Tool
vela.magazine.sequence_path
(vela magazine sequence path) is one of 10 tools on the
corpus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call vela.magazine.sequence_path from your client
- Claude Code corpus vela.magazine.sequence_path run in your project directory
- Claude Desktop corpus vela.magazine.sequence_path ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor corpus vela.magazine.sequence_path ~/.cursor/mcp.json
- VS Code corpus vela.magazine.sequence_path .vscode/mcp.json
- Zed corpus vela.magazine.sequence_path ~/.config/zed/settings.json
- Windsurf corpus vela.magazine.sequence_path ~/.codeium/windsurf/mcp_config.json
- Cline corpus vela.magazine.sequence_path ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI corpus vela.magazine.sequence_path ~/.gemini/settings.json
- Grok corpus vela.magazine.sequence_path .mcp.json (in your project root)
- ChatGPT corpus vela.magazine.sequence_path Settings → Connectors → Advanced → Developer mode
- Claude.ai corpus vela.magazine.sequence_path Settings → Connectors → Add custom connector
- LangChain corpus vela.magazine.sequence_path pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http corpus https://vela.study/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.