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