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, read and write, or manage account access, and okWOW checks your current permissions on every request. It reaches the spaces you have joined in your current organization.
Set up with your agent
Your agent can install okWOW and set up your account with you in the chat. In okWOW, open Settings > Authorized apps, select Set up with your agent, and paste the copied prompt into Claude Code, Codex or another agent.
If you are an agent following that prompt:
- Install the okWOW plugin with the commands for your app in Install the okWOW plugin. If you cannot install plugins (for example Claude on the web or ChatGPT), tell the user how to add the okWOW connector instead and wait for them to finish.
- Sign the user in. Start a new session, or reconnect the okWOW MCP server, so the browser opens okWOW. The user signs in and approves access. Recommend Read and write; an organization admin who wants to invite people chooses Manage account.
- Run
/okwow:setup. It reads the user's okWOW account and local agent setup first, asks only what it cannot see, then sets up spaces and sharing, invites (admins) or joins spaces and accepts invites (members), brings in transcripts and skills, offers to move local agent memory into okWOW, and sets session capture rules.
Adding plugins to okWOW, plans and billing stay in the okWOW app. Giving an agent access to your plugins is always your choice in Manage access; an agent cannot grant itself access.
Install the okWOW plugin
The okWOW plugin is the quickest way to connect Claude Code, Codex or Gemini CLI. It adds the okWOW connection and four skills: setup sets up your account in the chat, recall searches okWOW before your agent answers questions about past decisions and conventions, save stores a verified fact or artifact in the space you choose, and capture saves your coding sessions to okWOW.
Claude Code
Run these commands in your terminal:
claude plugin marketplace add ok-wow/plugin
claude plugin install okwow@okwow
Start Claude Code. Your browser opens okWOW once: follow the browser approval steps below. The okWOW tools and session capture share this one sign-in. In the session that was open while you signed in, run /mcp and reconnect plugin:okwow:okwow; later sessions connect on their own.
Codex
Run these commands in your terminal:
codex plugin marketplace add ok-wow/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. Codex signs its okWOW tools in on their own, so session capture opens okWOW once more for its own sign-in. Codex asks you once to trust the plugin's capture hooks, and again after a plugin update changes them.
Gemini CLI
Run this command in your terminal:
gemini extensions install https://github.com/ok-wow/plugin
Then run /mcp auth okwow in Gemini CLI and follow the browser approval steps below. The Gemini CLI extension includes the recall and save skills; it does not include setup or session capture.
These commands install the latest plugin and keep it up to date. To stay on one release instead, add its tag from the releases page: claude plugin marketplace add https://github.com/ok-wow/plugin.git#<tag> or codex plugin marketplace add ok-wow/plugin --ref <tag> or gemini extensions install https://github.com/ok-wow/plugin --ref <tag>.
Save your coding sessions
With the plugin installed, each Claude Code or Codex session is saved as one of your okWOW chats when it ends, or after 30 idle minutes. okWOW gives it a title and a summary and learns from it like a chat in the app. There is nothing to set up, and a resumed session adds its new turns to the same chat.
- Private to you. A saved session is your chat; other members cannot open it.
- Secrets stay on your machine. API keys, tokens, passwords, connection strings and the contents of credential files are redacted before upload, and okWOW redacts again before storing.
- You choose where sessions go. Ask your agent, for example “send this repo's sessions to Engineering” or “stop saving this folder.” It confirms each change before saving it. Rules apply by the folder or repository a session starts in.
Session capture needs Read and write access. Ask your agent “are my sessions going to okWOW?” to see the current state. Rules and pausing are also in okWOW under Settings > Authorized apps.
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
- Sign in to okWOW. Use the account whose knowledge and space permissions the agent should use.
- 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.
- Review the access request. The next consent screen identifies the agent requesting access. Review and approve read-only, read and write, or manage account access. Read-only allows finding and reading knowledge; read and write also allows creating memories and artifacts, creating and sharing spaces, and joining spaces where you have permission; manage account also lets an organization owner or admin invite people.
- 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 every space 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.
| Place | Who can access it | What the agent can create |
|---|---|---|
| Space you have joined in your current organization | Space members | Memories, memory groups, artifacts, files, skills, transcripts, and tasks, with an editor role or higher |
| Organization you belong to | Organization members | Memories, memory groups, artifacts, files, skills, and transcripts |
A space shared with specific people works like any other once you have joined it; pending invitations give no access. 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
| Tool | Purpose |
|---|---|
get_profile | Identify the connected account and its connection permissions. |
list_spaces | Discover the spaces and organizations you can use, with the operations available in each. |
search | Find accessible memories, tasks, and items in the Vault by text and meaning. |
fetch | Read one accessible item using an exact prefixed ID (memory:, vault:, or task: followed by a UUID) from search, a list, or a receipt. |
list_memories | List memories and memory groups, filtered by in or group. |
list_tasks | List tasks in a space. |
list_items | List the items in a space's Vault, or one kind, such as skills. |
search_entities | Find a person or subject, such as a project or customer, by name or identifier. |
get_node | Read one person, subject or space in the knowledge graph. |
list_edges | List what a person, subject or space is directly linked to. |
list_paths | Find who knows or owns a subject, how two are connected, or where an item came from. |
create_memory | Create reusable knowledge in an available space or organization, in an existing or new memory group. |
create_content | Create an artifact, file, skill, or transcript in an available space or organization. |
create_task | Record a task in a space. |
prepare_upload | Stage a file upload (upload:UUID) to attach with create_content or update_content. |
update_memory | Change a memory, or rename a memory group. Takes the version you last read. |
update_content | Change an artifact, file, skill, or transcript. Takes the version you last read. |
update_task | Start, change or finish a task. |
delete_content | Delete one memory, memory group, task or item in the Vault, for every member of its place. |
switch_mode | Set this connection to private or shared mode. See Private and shared mode. |
create_space | Create a space in your organization, private or shared with specific people or the whole organization. |
update_space | Join or leave a space, or change its name, description, audience or members. |
list_invites | List invitations you received and, for admins, the organization's pending invitations. |
create_invites | Invite people to your organization as admins or members. Organization owners and admins with manage account access. |
update_invite | Accept or decline an invitation you received, or revoke one your organization sent. |
get_session_capture | Show where your coding sessions from a folder are saved. |
set_session_capture_rule | Choose where sessions from a folder or repository are saved, or stop saving them. |
remove_session_capture_rule | Remove a session capture rule. |
Tools from okWOW plugins you gave this agent access to, such as email, chat, calendar or meetings, also appear, named <app>_<tool>. They act as you.
The create_*, update_*, delete_content and switch_mode tools require read and write access; inviting people and revoking invitations also require manage account 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, Read and write or Manage account access, connection date, and last-used date. The client ID may be a URL or an identifier rather than a friendly agent name.
Choose which plugins an agent can use
An agent can also use the plugins you added in okWOW, such as Gmail, Google Calendar, Google Drive or Linear, as its own tools. Select Manage access on the agent's row, then set each app to No access, Read or Read and write and choose which of its accounts the agent uses. One Google account covers its Gmail and Google Calendar tools. Nothing is shared until you choose it here.
Access is set per agent, not per connection: two connections from the same agent share it. A write still follows your permission level in okWOW, so an action that needs approval asks in okWOW before it runs. An agent connected read-only can only be given Read.
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.
The plugin's tools are missing or keep asking to sign in
Claude Code skips a plugin's server when another configured server uses the same URL, for example an okwow server you added by hand. Remove the other entry (claude mcp remove okwow -s user) and restart Claude Code, then check that /mcp lists plugin:okwow:okwow.
A space or action is missing
Ask the agent to call list_spaces. Check your current organization, membership in the 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.