Skip to content
Developers
GuidesAPI reference
slimwiki.comGet an API key

Guides

  • Quickstart
  • Authentication
  • Errors
  • Pagination
  • Rate limits
  • Content format
  • Versioning

Tools and agents

  • CLI
  • MCP server
  • Agent skill

API reference

  • Overview

Users

  • Retrieve the key ownerget

Accounts

  • List accountsget

Wikis

  • List wikisget
  • Retrieve a wikiget

Pages

  • List pages in a wikiget
  • Search pages in a wikiget
  • Find a page by slug or hashget
  • Create a pagepost
  • Retrieve a pageget
  • Delete a pagedelete
  • Archive a pagepost
  • Restore a pagepost

Guides

MCP server

SlimWiki runs an MCP server, so an AI assistant that supports the Model Context Protocol can read, search and create pages as tools, with nothing to install.

On this page

  • Connect
  • Connect by signing in
  • Connect with an API key
  • Tools
  • What to expect

Connect

The server speaks MCP over HTTP (the Streamable HTTP transport) at one address:

MCP server URL
https://api.slimwiki.com/mcp

There are two ways to connect. Both act as you, with your access.

  • Sign in. Give your assistant the URL. It opens SlimWiki in your browser, you sign in and choose Allow, and it is connected. Nothing to copy.
  • API key. For scripts and for clients that cannot open a browser, send a key in a header, as for the API.

Connect by signing in

In an assistant that supports remote MCP servers, add a server (often called a connector) with the URL above. In Claude Code:

Claude Code
claude mcp add --transport http slimwiki https://api.slimwiki.com/mcp

The first time the server is used, your browser opens SlimWiki. The page shows the name the app gave itself, what it will be able to do, and the address it will return you to. Choose Allow to connect or Deny to refuse.

What an app can ask for
PermissionLets the app
wiki:readRead the wikis and pages you can see.
wiki:writeCreate, archive and restore pages as you.
offline_accessStay connected without asking you to sign in again each hour.

For people building an MCP client

The server follows the MCP authorization flow: OAuth 2.1 authorization code with PKCE (S256). A request without credentials gets a 401 whose WWW-Authenticate header points at the protected resource metadata; from there you can discover the authorization server and register your client dynamically. Access tokens last one hour; refresh tokens last 30 days and are replaced each time they are used.

Connect with an API key

Create a key in SlimWiki under Profile → API keys (see Authentication) and send it as a bearer token. In Claude Code, with the key in the SLIMWIKI_API_KEY environment variable:

Claude Code
claude mcp add --transport http slimwiki https://api.slimwiki.com/mcp \
  --header "Authorization: Bearer $SLIMWIKI_API_KEY"

Clients configured with a JSON file use an entry of this shape:

MCP client configuration
{
  "mcpServers": {
    "slimwiki": {
      "type": "http",
      "url": "https://api.slimwiki.com/mcp",
      "headers": {
        "Authorization": "Bearer swk_your_key"
      }
    }
  }
}

A key in a config file is a secret

Keep configuration files that contain a key out of version control, and prefer a read-only key when the assistant only needs to look things up.

Tools

MCP tools
ToolWhat it doesNeeds
whoamiReturns the user the connection acts as.Read access
list_accountsLists the accounts the user belongs to.Read access
list_wikisLists the wikis in an account.Read access
list_pagesLists the pages in a wiki, without their content.Read access
search_pagesSearches the titles and content of the pages in a wiki.Read access
get_pageReturns one page with its content.Read access
create_pageCreates a page, optionally under another page.Write access
archive_pageMoves a page to the archive.Write access
restore_pageBrings an archived page back.Write access

Each tool is one call to the API and returns that endpoint's JSON response, so the API reference describes the fields. A request the API refuses comes back as a tool error carrying the usual error body.

What to expect

  • Your access, no more. The assistant acts as the person who signed in or created the key and can reach only what they can. A read-only key, or a connection allowed for reading only, cannot create, archive or restore pages.
  • No permanent delete. There is no tool to delete a page. An assistant can archive a page, which can be undone.
  • No editing existing pages. As with the API, content is set when a page is created; see Content format.
  • Rate limit. Every tool call counts as one request towards the connection's limit of 120 requests per minute. See Rate limits.
  • No sessions. The server keeps no state between requests and accepts POST only.

Previous

CLI
Work with your wikis from the terminal: sign in, find pages and create them.

Next

Agent skill
A ready-made skill that teaches an AI agent how to work with SlimWiki.

SlimWiki Developers

slimwiki.com