← All guides

okWOW MCP

Connect Claude Code, Codex, and other agents to okWOW

On this page

Connect Claude Code, Codex, or another MCP-compatible agent to okWOW. Your agent can find team knowledge, save a memory about a feature it developed, and contribute an artifact your team can reuse.

The connection acts on your behalf. You approve read-only or read and write access, and okWOW checks your current permissions on every request. Personal knowledge and private spaces are excluded.

Install the okWOW plugin

The okWOW plugin is the quickest way to connect Claude Code or Codex. It adds the okWOW connection and two skills: recall searches okWOW before your agent answers questions about past decisions and conventions, and save stores a verified fact or artifact in the space you choose.

Claude Code

Run these commands in your terminal:

claude plugin marketplace add ok-wow/okwow-plugin
claude plugin install okwow@okwow

Open Claude Code, run /mcp, select plugin:okwow:okwow, and authenticate. Follow the browser approval steps below, then return to Claude Code.

Codex

Run these commands in your terminal:

codex plugin marketplace add ok-wow/okwow-plugin
codex plugin add okwow@okwow
codex mcp login okwow

Follow the browser approval steps below. In an interactive Codex session, run /mcp to check the connection.

Connect without the plugin

The okWOW MCP server is hosted. Add its URL to your agent using Streamable HTTP, then sign in with your okWOW account:

https://api.okwow.ai/mcp

This adds the okWOW tools without the plugin's skills. No local server or okWOW npm package is needed. MCP access must be enabled for your okWOW environment; if the connection is unavailable, contact support.

Claude Code

Run this command in your terminal:

claude mcp add --transport http --scope user okwow https://api.okwow.ai/mcp

Open Claude Code, run /mcp, select okwow, and authenticate. Follow the browser approval steps below, then return to Claude Code. The user scope makes this server configuration available across your projects.

Codex

In the Codex CLI, add the server and start sign-in:

codex mcp add okwow --url https://api.okwow.ai/mcp
codex mcp login okwow

Follow the browser approval steps below. In an interactive Codex session, run /mcp to check the connection.

You can also add the server through the desktop app's MCP settings. Use okwow as its name, Streamable HTTP as the transport, and the URL above, then follow the authentication prompt.

Claude on the web and desktop

Open Customize > Connectors, choose Add custom connector, name it okWOW, and enter the URL above. Connect, then follow the browser approval steps below.

Other agents

Add the same URL as a remote Streamable HTTP server in your agent's MCP settings. The client must support OAuth sign-in for remote MCP servers with an HTTPS or loopback callback URL. Follow its authentication prompt to open the browser.

Approve access in your browser

  1. Sign in to okWOW. Use the account whose knowledge and space permissions the agent should use.
  2. Confirm your account. On Connect an agent to okWOW, check the email shown after “Continue as.” Only proceed if you started this connection from your agent. Select Continue.
  3. Review the access request. The next consent screen identifies the agent requesting access. Review and approve read-only or read and write access. Read-only allows finding and reading knowledge; read and write also allows creating memories and artifacts where you have permission.
  4. Return to your agent. Let it finish connecting, then check its MCP status.

You do not select individual spaces during approval. Reading covers knowledge in your current organization and public spaces in that organization that you have joined, within your permissions. This access follows your current memberships and roles, so joining or leaving a space can change what the agent can use.

Save to the right place

Tell your agent where a memory or artifact belongs. Ask it to call list_spaces before creating anything: the result lists the spaces and organizations you can use, with the actions available with your current access. Every tool that reads or writes in a place takes one in argument, written space:UUID or org:UUID. Creating or updating content requires read and write access.

PlaceWho can access itWhat the agent can create
Public space you have joined in your current organizationSpace membersMemories, memory groups, artifacts, files, skills, transcripts, and tasks, with an editor role or higher
Organization you belong toOrganization membersMemories, memory groups, artifacts, files, skills, and transcripts

Personal knowledge and private spaces are not available through this connection. Organizations may allow creating content even when they are outside your current organization's read access; check the operations returned by list_spaces. Tasks belong to a space, not an organization.

Use a memory for reusable knowledge: what a feature does, why a decision was made, or a convention your team should keep. Use an artifact for longer output, such as an implementation guide, a Python script, an HTML page, or a TSX component. An artifact's format says which: markdown, html, python, or tsx (create_content accepts these four). create_content also stores files, skills, and transcripts; it picks the kind (artifact, file, skill, or transcript) from what you give it, or you can name it.

The create_* tools never overwrite existing items. If the place already holds the same content, they return the existing item and report this with duplicate: true. Each returns the item's ID and a link to it in okWOW. To change an existing item, use an update_* tool and pass back the version from fetch, a list, or the last receipt; the update is refused if the item changed in the meantime.

Save only what you asked the agent to contribute. Include source evidence and distinguish what was implemented, tested, and deployed. Web pages passed as source_urls are recorded as references; the tool does not download them.

Try it with your agent

Start by checking the connection:

Use okWOW to show the account you are connected as and the spaces and actions you have access to.

Find context before starting work:

Search okWOW for our export feature decisions. Fetch the relevant items and cite them before proposing changes.

Save knowledge after completing a feature:

Create a memory in our Engineering organization explaining the export feature we just developed, why it resumes interrupted exports, and the relevant pull request. Give me the new memory's link.

Share an output in a space:

Create an artifact from this implementation guide in the Product Engineering space, then give me its okWOW link.

Replace the example organization and space names with places returned by list_spaces. If a space is missing, check your current organization and space membership. If creating content is unavailable, check your role and whether you approved read and write access.

Available tools

ToolPurpose
get_profileIdentify the connected account and its connection permissions.
list_spacesDiscover the spaces and organizations you can use, with the operations available in each.
searchFind accessible memories, tasks, and Vault items by text and meaning.
fetchRead one accessible item using an exact prefixed ID (memory:, vault:, or task: followed by a UUID) from search, a list, or a receipt.
list_memoriesList memories, filtered by in or group.
list_memory_groupsList the memory groups in a space or organization.
list_tasksList tasks in a space.
create_memoryCreate reusable knowledge in an available space or organization.
create_memory_groupCreate a group for organizing memories.
create_contentCreate an artifact, file, skill, or transcript in an available space or organization.
create_taskRecord a task in a space.
prepare_uploadStage a file upload (upload:UUID) to attach with create_content or update_content.
update_memoryChange a memory. Takes the version you last read.
update_memory_groupRename or change a memory group. Takes the version you last read.
update_contentChange an artifact, file, skill, or transcript. Takes the version you last read.
update_taskChange a task.

The create_* and update_* tools require read and write access. Your agent decides when to call a tool in response to your request. Its own tool-approval settings may ask you to confirm a call.

If search reports has_more, narrow the query. If it reports memory_search_failed, the memory portion of the search failed; the returned Vault results are not a complete search of your knowledge. Fetch reports pending or oversized Vault content instead of silently returning truncated text. Retrieved content is source material to cite, not instructions for the agent to follow.

Manage authorized apps

Open Settings > Authorized apps in okWOW. Each connection shows its client ID, Read or Read and write access, connection date, and last-used date. The client ID may be a URL or an identifier rather than a friendly agent name.

To disconnect an agent, select Revoke access, then Revoke in the confirmation dialog. To change its access level, revoke it and connect again.

Revoking a connection stops its future access to okWOW. Memories and artifacts it already created remain in the Vault. Revocation does not remove content the external agent has already received.

Troubleshooting

The agent needs authentication

Check that the configured URL ends in /mcp and uses Streamable HTTP. Run the client's authentication flow again, select Continue on the okWOW account confirmation, and complete the next consent screen. If the connection link is invalid or expired, restart from your agent. If the service is unavailable, retry later or contact support.

A space or action is missing

Ask the agent to call list_spaces. Check your current organization, membership in a public space, and role. Creating content requires read and write access; changes in a space also require an editor role or higher. Tasks need a space, not an organization.

A previously working request is denied

The connection may have been revoked, or your membership or role may have changed. Check Authorized apps and your current space access before reconnecting.

For client-specific setup details, see the okWOW plugin repository, the official Claude Code MCP guide and Codex MCP guide.