WolfSuiteWolfXLWolfPPTWolfDocxWolfRender

WolfSuite Workspace · MCP guide

Connect an MCP client to WolfSuite Workspace

Give your agent access to a shared WolfSuite Workspace where you can review its proposed edits to Word, Excel and PowerPoint files.

Use your workspace address

https://NAME.workspace.wolfsdk.com/mcp

Replace NAME with the name in your confirmed workspace address. Add the endpoint as a remote HTTP MCP server. With OAuth, sign in to that workspace in your browser, check the requesting application and approve the connection. Your client receives its own token.

Verification and source references

Service and sign-in tests: sdk/web/packages/control-plane/src/oauth.ts and sdk/web/packages/control-plane/test/oauth.test.ts.

Set up your client

Use your own workspace name in the examples below. These are configuration examples; availability of custom connectors depends on your client and account.

Claude

Add a custom connector in Settings → Connectors. Name it Wolf Workspace, paste this remote server URL, then connect.

https://NAME.workspace.wolfsdk.com/mcp

Claude Code

In a terminal (bash or zsh), add the server. In Claude Code, open /mcp and authenticate.

claude mcp add --transport http wolf https://NAME.workspace.wolfsdk.com/mcp

ChatGPT

In an account with developer mode and custom apps enabled, create an app in Settings → Apps. Choose OAuth and use this MCP server URL.

https://NAME.workspace.wolfsdk.com/mcp

Cursor

Add this entry to your MCP configuration, then connect the server.

{
  "mcpServers": {
    "wolf": {
      "url": "https://NAME.workspace.wolfsdk.com/mcp"
    }
  }
}

Codex

Add the server and sign in from a terminal (bash or zsh).

codex mcp add wolf --url https://NAME.workspace.wolfsdk.com/mcp
codex mcp login wolf

Client instructions: Claude, Claude Code, ChatGPT, Cursor, Codex.

Connect an agent with a device code

  1. POST a JSON object such as {"agent_name":"My agent"} to /-/connect on your workspace. Keep the returned device code private.
  2. Show the person the verification URI and user code. The person signs in, enters the code and approves only the request they started.
  3. POST the device code as device_code to /-/connect/token at the returned interval. Wait on authorization_pending, back off on slow_down, and stop on denial or expiry.
  4. Use the returned mcp_url and send Authorization: Bearer followed by the access token. Store it privately. A guest token is limited to the shared document; a member token acts for the approving member.

Full device-flow and guest instructions (Workspace service guide, November 20, 2026).

Verification and test references

Implementation test: sdk/web/packages/control-plane/test/connect.test.ts.

The eight Workspace tools

workspace_list
Find documents and their head revisions, pack bindings, open proposals and comment threads.
doc_read
Read a document at its current revision. Request text, structure or Markdown; use the cells view for a workbook.
doc_search
Search text and cell values. Use the address in a hit to read the matching passage or cell.
doc_create
Create a Word, Excel or PowerPoint file from a blank document or a template.
doc_edit
Send a batch of edits against the revision you read. Choose propose for review or, if authorized, commit to change the document immediately.
doc_inspect_visual
Inspect a page or proposal preview as PNG, or ask for page count and size first. Requires rendering support on the server.
pack_link_refresh
Refresh existing bindings from spreadsheet sources to Word or PowerPoint targets. Choose propose to review the updates.
comment_reply
Reply to an existing thread by ID. Mention a collaborator or resolve the thread with your reply.
Contract and test references

Tool contract: sdk/web/packages/protocol/src/workspace/mcp.ts. Behavior tests: sdk/web/packages/mcp/test/tools.test.ts and sdk/web/packages/mcp/test/workflow.test.ts.

Continue with MCP