Your custom skills were built for you. A prompt that extracts talking points, a review checklist, a workflow you refined over months of conversations. They work. And nobody else on your team can use them, because they live in your config on your machine.
Theona is where teams keep their agents: shared spaces, shared knowledge, agents any teammate can run. The Theona MCP server now ships migration tooling that closes the gap between the two. Connect it to Claude, Codex, or any other MCP-compatible client and ask your assistant to import your workflows. What you built for yourself becomes something your team can run.
What a Migration Looks Like
First, what moves. Workflows here means your recurring work: the custom skills in your config, the routines you’ve automated, the tasks you ask for again and again. That’s what becomes agents. One-off chat requests don’t; they stay in the chat.
Two AI actors split the job. Your Claude or Codex assistant drives the migration from the client side. The Architect, Theona’s built-in agent that designs other agents, builds everything on the Theona side. The only prerequisite is a Theona account (sign up at app.theona.ai); the Architect takes care of the rest, including a place for the new agents to live.
Once the server is connected (setup is in How to Connect below), tell your assistant: “Import my workflows into Theona.” The MCP server hands it a migration playbook. You stay in the loop for a few confirmations; the two of them handle the rest.
The Inventory
Your assistant starts by looking at your recurring work: the tasks you keep asking for, the skills you’ve accumulated, the external services they touch. It drafts a list of migration candidates and confirms it with you. You decide what moves and what stays in the chat before anything gets built.
The Architect Takes Over
Your assistant opens a session with the Architect and describes each workflow from the list: what it does, its inputs and outputs, which services it needs.
The Architect starts with a home for the agents. It reuses a space (a workspace that combines agents with a shared knowledge base) if your team already has one, or creates a new one, and loads the knowledge base with the material your workflows depend on: style guides, reference docs, exported notes. The agents will work from the same material you do, and so will every teammate who runs them after you.
Then it builds, one agent at a time, asking follow-up questions and proposing how to group related steps. The grouping is where the value shows. In one real migration, fifteen Claude Code skills became twelve agents in a single session. A four-step content workflow (extract talking points, enrich with research, draft the post, review it) collapsed into one agent that runs end to end.
OAuth Stays in Your Browser
When an agent needs a third-party service like Slack, Gmail, Notion, or GitHub, the Architect sends a connection link. You open it in your browser, complete OAuth on theona.ai, and the session resumes on its own. Your assistant never sees a password or an API key. Credentials go straight from you to the service.
Every finished agent comes back with a URL. Open it, run it, or ask the Architect to put it on a schedule.
How to Connect
The server is live at https://api.theona.ai/mcp. Setup depends on your client.
Claude Desktop
- Open Customize → Connectors → “+” → Add custom connector
- Set the Remote MCP Server URL to https://api.theona.ai/mcp
- Click Add, then allow access when your browser prompts you
Claude Code
Add the Theona server:
claude mcp add --transport http theona https://api.theona.ai/mcpThen authenticate:
- Run Claude Code
- Type
/mcp - Select Theona from the list
- Select Authenticate
- Allow access when your browser prompts you
Codex in the ChatGPT desktop app
- Open Settings → Plugins → MCPs → Add server
- Name the server
theona - Set the type to Streamable HTTP
- Enter https://api.theona.ai/mcp as the URL
- Click Save and authenticate when prompted. Leave the bearer token and headers empty; Theona uses OAuth
Codex CLI
Add the server to ~/.codex/config.toml (or .codex/config.toml for a single project):
[mcp_servers.theona]
url = "https://api.theona.ai/mcp"Then authenticate:
codex mcp login theonaStart a Codex session and run /mcp to confirm Theona is connected.
Other MCP-Compatible Clients
Any client that supports remote MCP servers over HTTP transport can connect. Cursor and Windsurf walkthroughs are in our MCP announcement; for anything else, check your client’s documentation for where to add remote servers.
Why We Built This
Theona is built around one idea: AI agents should fit into how people already work. For a team, that means one home for its agents. A place where they’re shared and visible, instead of scattered across personal configs and chat histories.
MCP keeps that home open in both directions. Migration brings your personal workflows into the team’s space. The same server lets you run the team’s agents from the client you already work in. Your team gets a shared agent library, and you keep your favorite tools.
A skill in your Claude config helps one person. The same skill as a Theona agent runs on a schedule, connects to more than sixty services, and shows up for every teammate who needs it. Migration is the path from one to the other, and now it starts with a single prompt.
Connect the server and say the word. Your workflows will follow.