Skip to main content

​
Overview

The Model Context Protocol (MCP) server brings Wolfia AI into the tools your team already works in, so they can chat, search, and pull answers without leaving their editor or terminal. 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.
Connecting directly without the shim, putting Wolfia behind a gateway (Runlayer, Cloudflare AI Gateway, etc.), or hitting an Invalid redirect URI error? See MCP OAuth, direct connections & gateways for the full OAuth contract, redirect URI rules, and why Wolfia needs no manual allowlist.

​
Supported clients

​
Available tools

Once connected, your client can chat with Wolfia AI, search your knowledge base and Slack history, read documents, submit questionnaires, and manage knowledge and settings, all scoped to your Wolfia permissions.

Browse every MCP tool

See the full tool reference, grouped by category (chat, knowledge search, documents, Slack, questionnaires, knowledge management, AI customization, and trust center), with what each tool does and which role it needs.
Every tool respects your organization’s permissions, so you only see and change content you already have access to in Wolfia.

​
Setup

​
Claude Code

Add Wolfia with a single command:

​
Cursor / Windsurf

Add the following to your MCP configuration file:

​
Claude Desktop

Edit claude_desktop_config.json (Settings, then Developer, then Edit Config):

​
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):
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:
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

​
Invalid redirect URI

The client (or your gateway) sent a redirect URI that Wolfia rejects. There is no Wolfia-side allowlist to change, the fix lives in your client or gateway config. See MCP OAuth: redirect URI rules and troubleshooting for the exact rules and how to fix it.

​
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)