Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.wolfia.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Wolfia provides an MCP (Model Context Protocol) server that lets your internal users chat with Wolfia AI and search your organization’s knowledge base, documents, and Slack history directly from any MCP-compatible AI tool. Authentication is handled via OAuth, so you sign in once with your existing Wolfia account and the client stays connected. The server is hosted at https://api.wolfia.com/mcp/ and uses mcp-remote as a thin stdio shim that most clients already know how to spawn.

​
Supported clients

ClientType
Claude CodeCLI / Terminal
Claude DesktopDesktop app
CursorIDE
WindsurfIDE
OpenClawLocal AI agent
Any other MCP-compatible client (custom agents, desktop apps)Desktop / CLI / Agent

​
Available tools

ToolDescription
send_messageAsk Wolfia AI a question and get an expert answer with citations, using the full Wolfia answering pipeline
list_conversationsList your recent Wolfia conversations
get_conversationRetrieve a full conversation with all messages and citations
search_knowledgeSemantic vector search across your organization’s entire knowledge base. Filter by source type and tags. Returns facts grouped by source with similarity scores
search_knowledge_textFull-text keyword search across all indexed facts. Use when you know the exact terms (e.g. “SOC 2”, “rate limiting”)
list_sourcesBrowse and filter content sources by source type (Notion, Slack, Google Drive, etc.), name, or tags. Returns document IDs and download URLs
get_document_contentRead the full raw content of a document: Notion page as markdown, Slack conversation, or uploaded file, plus extracted facts and the source URL
get_document_download_urlsGet presigned S3 download URLs (for files) or direct URLs (for web pages) for a batch of document IDs
search_slack_messagesSearch raw Slack messages by text. Optionally filter to a specific channel. Returns sender, channel, and a deep link to the thread
get_slack_threadRead a complete Slack thread with all replies, sender names, emails, and reactions
list_integrationsList all connected integrations (Notion, Slack, Google Drive, etc.), document counts, and last sync time
Each tool respects your organization’s permissions, so you only see content you already have access to in Wolfia.

​
Setup

​
Claude Code

Add Wolfia with a single command: 
claude mcp add wolfia -- npx -y mcp-remote@latest https://api.wolfia.com/mcp/

​
Cursor / Windsurf

Add the following to your MCP configuration file:
ClientConfig file location
Cursor.cursor/mcp.json in your project or global settings
Windsurf.windsurf/mcp.json or IDE settings
{
  "mcpServers": {
    "wolfia": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://api.wolfia.com/mcp/"]
    }
  }
}

​
Claude Desktop

Edit claude_desktop_config.json (Settings, then Developer, then Edit Config): 
{
  "mcpServers": {
    "wolfia": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://api.wolfia.com/mcp/"]
    }
  }
}

​
OpenClaw

OpenClaw can spawn standard stdio MCP servers. Add Wolfia to your OpenClaw MCP config (typically ~/.openclaw/mcp.json or the equivalent in your OpenClaw settings): 
{
  "mcpServers": {
    "wolfia": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://api.wolfia.com/mcp/"]
    }
  }
}
On first use, OpenClaw will launch a browser window for OAuth sign-in. After you authorize, all Wolfia tools become available to your local agent.

​
Other MCP clients (custom agents, desktop apps)

Any client that can spawn a stdio MCP server works. Point it at mcp-remote with the Wolfia endpoint: 
{
  "mcpServers": {
    "wolfia": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://api.wolfia.com/mcp/"]
    }
  }
}
If your client speaks remote MCP (streamable HTTP) natively without a stdio shim, connect directly to https://api.wolfia.com/mcp/ and let the client handle the OAuth dance.
After editing the config file, restart your application for changes to take effect.

​
Authentication

The first time you use Wolfia, you’ll be prompted to authenticate:
  1. A browser window opens automatically
  2. Sign in with your existing Wolfia account (SSO or email)
  3. Authorize the application to access Wolfia
  4. Return to your app, you’re now connected
Tokens are cached locally by mcp-remote (typically under ~/.mcp-auth/), so you only sign in once per client.
You must have an existing Wolfia account to use the MCP server. If you don’t have one, sign up at wolfia.com first.

​
Troubleshooting

​
Authentication errors

If authentication fails:
  • Clear your browser cookies for wolfia.com and try again
  • Clear the local mcp-remote token cache (rm -rf ~/.mcp-auth) and reconnect
  • Ensure you’re using the same account that has access to your Wolfia organization

​
Tools don’t appear

  • Restart the client after editing the config file
  • Check that npx is on your PATH (npx --version)
  • Check your client’s MCP logs. Claude Code: claude mcp list. Cursor/Windsurf: MCP panel in settings

​
Requirements

  • An MCP-compatible client
  • A Wolfia account with access to your organization
  • Node.js 18+ (for npx)