gitbook_get_space — GitBook MCP by usefulapi MCP Tool
gitbook_get_space
(gitbook get space) is one of 14 tools on the
GitBook MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call gitbook_get_space from your client
- Claude Code GitBook MCP by usefulapi gitbook_get_space run in your project directory
- Claude Desktop GitBook MCP by usefulapi gitbook_get_space ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GitBook MCP by usefulapi gitbook_get_space ~/.cursor/mcp.json
- VS Code GitBook MCP by usefulapi gitbook_get_space .vscode/mcp.json
- Zed GitBook MCP by usefulapi gitbook_get_space ~/.config/zed/settings.json
- Windsurf GitBook MCP by usefulapi gitbook_get_space ~/.codeium/windsurf/mcp_config.json
- Cline GitBook MCP by usefulapi gitbook_get_space ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GitBook MCP by usefulapi gitbook_get_space ~/.gemini/settings.json
- Grok GitBook MCP by usefulapi gitbook_get_space .mcp.json (in your project root)
- ChatGPT GitBook MCP by usefulapi gitbook_get_space Settings → Connectors → Advanced → Developer mode
- Claude.ai GitBook MCP by usefulapi gitbook_get_space Settings → Connectors → Add custom connector
- LangChain GitBook MCP by usefulapi gitbook_get_space pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gitbook https://gitbook.usefulapi.io/mcp
Other tools on this server
- gitbook_get_current_user
- gitbook_list_organizations
- gitbook_list_spaces
- gitbook_list_pages
- gitbook_get_page
- gitbook_search_space
- gitbook_search_organization
- gitbook_list_collections
- gitbook_get_collection
- gitbook_list_change_requests
- gitbook_list_comments
- gitbook_create_change_request
- gitbook_update_change_request
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.