ClaudeMCPKnowledge management

How to Give Claude Access to Company Docs (Without Uploading Them)

Connect Claude to live company docs over MCP — Claude Code, OAuth, and what stays in your workspace. No zip upload.

Wyatt Team5 min read

The usual way to “give Claude the docs” is to upload them. A zip into a Project. A paste into the prompt. A Drive connector on a Team plan. That works until the doc changes, the file cap hits, or you do not want the corpus sitting in the chat product.

There is a cleaner pattern: Claude calls tools against the workspace that already holds the docs. Wyatt exposes that as a remote MCP server. You authorize it with OAuth. You do not create or paste an API key.

This is the setup as of 14 August 2026. The commands below match Wyatt’s MCP quickstart. Claude.ai Projects are a different product — this is not a toggle inside a Claude Project.

What you are connecting

Model Context Protocol lets an AI client discover and call tools on another service. Wyatt is the server. Claude Code (or Cursor, Codex, ChatGPT, OpenClaw) is the client.

The endpoint:

https://www.wyattworks.ai/api/mcp-server

Use Streamable HTTP and OAuth. Wyatt publishes authorization metadata, so the client opens a browser grant instead of asking you for a token.

During approval you choose:

  • which workspaces the client may reach
  • read-only or full access

Each tool call stays inside that grant and your current membership. An inactive refresh grant expires after seven days. Reconnect when it expires. Log out of the Wyatt server in the client to drop stored authorization.

Claude Code (the path this post is for)

Install and log in to Claude Code, then:

claude mcp add --transport http --scope user wyatt https://www.wyattworks.ai/api/mcp-server
claude mcp list

Start Claude Code and run /mcp to finish or inspect authorization.

Then, in a new session, ask something that cannot succeed unless the tools work:

List the Wyatt workspaces I can access, then tell me which Wyatt tools are
available. Do not modify anything.

If authorization succeeded but no workspace appears, you did not approve a workspace, or you are no longer a member of it.

From there the useful prompts look like work, not setup:

Search Wyatt for the Q3 launch brief. Cite the document. List open tasks
in that project. Do not create anything yet.

Claude is reading the live workspace, not a snapshot you uploaded last Thursday.

If you are not on Claude Code

Same endpoint, same OAuth. Wyatt documents these clients:

Cursor — add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "wyatt": {
      "url": "https://www.wyattworks.ai/api/mcp-server"
    }
  }
}

Then Cursor Settings > Tools & MCP, enable Wyatt, complete OAuth.

Codex

codex mcp add wyatt --url https://www.wyattworks.ai/api/mcp-server
codex mcp login wyatt
codex mcp list

ChatGPT — enable developer mode under Settings > Apps > Advanced settings, then Apps > Create. Name the app Wyatt, enter the endpoint, choose OAuth, scan tools, sign in. Workspace admins control whether custom apps are allowed.

OpenClaw

openclaw mcp set wyatt '{"url":"https://www.wyattworks.ai/api/mcp-server","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login wyatt
openclaw mcp doctor wyatt --probe

If OpenClaw prints a code after browser approval, finish with openclaw mcp login wyatt --code <code>.

A client that will only accept a pasted API key cannot use this flow.

What this is not

It is not “upload the handbook into a Claude Project.” Projects are a knowledge pack inside Claude. MCP is Claude reaching out.

It is not Claude Team’s built-in connectors to Drive, Slack, or Microsoft 365. Those search those apps from Claude. They do not make Wyatt (or your tasks and docs) the system of record.

It is not a permanent org-wide integration you set once for every employee. Each person authorizes the client they use. Grants go stale after a week idle. That is the point: access is scoped, reviewable, and expires.

Why teams search for this

ChatGPT and Claude both added Projects so you can stop re-pasting. The limit is the pack: ChatGPT caps project files at 5 / 25 / 40 depending on plan. A company corpus is larger than that, changes daily, and already lives in a workspace.

If the assistant can search that workspace and cite the page, you do not maintain a second copy for the model.

Frequently asked questions

Does this work in claude.ai in the browser?

Wyatt’s documented Claude path is Claude Code. Browser Claude can use Team connectors and Projects. Connecting Wyatt MCP from claude.ai is not a documented setup, so do not assume a Projects toggle will appear.

Do I need Claude Team?

Not for MCP. You need a Claude Code (or other client) login and a Wyatt workspace you belong to. Team is what you buy for Claude’s own sharing, SSO, and connectors.

Can the agent edit my docs?

Only if you grant full access at OAuth time. Start read-only. Ask it to list tools and search before you grant writes.

Is there an API key?

No. If a tutorial tells you to paste a Wyatt secret into MCP config, it is not this server.

Try it on a real project

Wyatt is free during beta. A useful hour:

  1. Create a workspace and paste a brief into a document — or import a Notion page by pasting the link.
  2. Put the follow-ups on tasks in the same project.
  3. Connect Claude Code with the command above.
  4. Ask what is blocked, with citations.

Setup detail lives in Understand MCP. If you are choosing a chat folder rather than a workspace, see ChatGPT Projects vs Claude Projects.

More from the Wyatt blog