MCP Tools Catalog
Pro Available on the Pro tier.
The Inklings MCP server exposes workspace tools and resources over Streamable HTTP. External agents — Claude Code, Cursor, or any MCP-compatible client — use these to read, search, and write your workspace content.
All endpoints require Authorization: Bearer <token> except /health.
Page tools
Section titled “Page tools”| Tool | Description | Parameters |
|---|---|---|
create_page | Create a new page in the workspace | title (string), content (string, optional), parent_slug (string, optional) |
read_page | Retrieve full content and metadata for a page | slug (string) |
update_page_content | Replace the content of a page | slug (string), content (string) |
delete_page | Move a page to trash (soft delete) | slug (string) |
search | Search pages by content and title | query (string) |
Tool result format
Section titled “Tool result format”All tools return a CallToolResult with an array of content items:
{ "content": [ { "type": "text", "text": "..." } ], "isError": false}On error, isError is true and the text field describes the failure.
create_page
Section titled “create_page”Creates a real page in the open workspace. Returns the new page’s slug, title, and page_id.
{ "title": "Dragon Lore", "content": "Dragons breathe fire and hoard treasure.", "parent_slug": "bestiary"}read_page
Section titled “read_page”Returns the page’s title, content, word count, and timestamps. Content matches what was last saved in the editor.
{ "slug": "dragon-lore"}search
Section titled “search”Returns an array of search hits. Each hit includes slug, title, snippet, and score. Results are ranked by relevance.
{ "query": "dragon fire"}delete_page
Section titled “delete_page”Moves the page to trash — not permanent deletion. The page is recoverable via Trash in the Inklings app.
{ "slug": "dragon-lore"}Resources
Section titled “Resources”Resources are read via read_resource with a URI.
| Resource URI | Description | MIME type |
|---|---|---|
inklings://workspace/tree | Full workspace page hierarchy | application/json |
inklings://workspace/page/<slug> | Page content by slug | text/plain |
inklings://workspace/search?q=<query> | Search results | application/json |
inklings://workspace/tree
Section titled “inklings://workspace/tree”Returns the complete workspace page hierarchy as a JSON array. Each node includes slug, title, has_children, and a children array.
[ { "slug": "world-overview", "title": "World Overview", "has_children": true, "children": [ { "slug": "geography", "title": "Geography", "has_children": false, "children": [] } ] }]Authentication
Section titled “Authentication”| Endpoint | Auth required |
|---|---|
/mcp | Yes — Authorization: Bearer <token> |
/health | No |
Invalid or missing tokens receive HTTP 401. The server uses constant-time comparison to evaluate tokens.
Server limits
Section titled “Server limits”| Limit | Value |
|---|---|
| Request timeout | 60 seconds |
| CORS allowed origins | http://127.0.0.1 only |
| Allowed methods | GET, POST |
Built-in agent tools vs MCP tools
Section titled “Built-in agent tools vs MCP tools”The Inklings built-in agent uses a separate (richer) tool set than the MCP server exposes. The built-in agent tools include get_backlinks, get_outgoing_links, move_page, rename_page, and other workspace operations not yet available via MCP.
See Agent Tools for the built-in agent tool catalog.
See Also
Section titled “See Also”- MCP Server — Enable the server and get your bearer token
- Agent Tools — Tools available to the built-in agent
- Settings Reference — MCP server settings
Was this page helpful?
Thanks for your feedback!