
Argentic
io.github.Argentic-Labs-AIPublished by GitHub account Argentic-Labs-AIv0.3.2Updated Nov 1, 2026
Argentic MCP server: run and inspect long-running agents on Argentic.
Overview
Remote MCP server for Argentic that lets an assistant wake, inspect, resume and approve long-running agents that keep memory between calls.
- What you can do
- Wake agents, fire due wakes, resume or replay runs, and list agents, wakes and due work
- Inspect a single wake and answer pending approvals (approval answering needs an owner or admin role)
- Manage the account: read account details, list, create and revoke API keys, check usage and set a budget
- Read-only status skills list agents and which runs were cut off, and help diagnose why a run stopped
- When to use it
- Useful when you run agents on Argentic and want a coding assistant to start them, check what they remember, recover interrupted runs, or manage keys, usage and budget from the same chat.
- Requirements
- A remote endpoint at getargentic.com/mcp over streamable HTTP. Sign-in uses OAuth with an Argentic account and an organization selection. Waking an agent also needs your own model-provider key, sent in the X-Model-Key header (x-api-key on claude.ai); Argentic does not store it. The optional CLI demo needs Node 22 or newer and an Argentic API key.
Installation
In SourceWeft
- Open Argentic in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Argentic-Labs-AI%2Fargentic/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"argentic": {
"type": "http",
"url": "https://getargentic.com/mcp"
}
}
}README
Argentic plugins
Connect your coding agent to Argentic: wake agents that keep their memory between calls, read what they remember, give them tools, and manage your API keys, usage and budget.
This repo holds only manifests, skills, MCP settings and small client adapters. The engine is not in it.
There is one MCP, https://getargentic.com/mcp. You sign in with your Argentic account (OAuth) and pick an organization. No API key is needed for the MCP. To wake an agent you also need your own key for a model provider; it travels in the X-Model-Key header on each request and Argentic never stores it.
Kill it mid-run (2 minutes)
You need an Argentic API key from https://getargentic.com/platform and a model key. The default model is a free NVIDIA one; get its key at https://build.nvidia.com. Node 22 or newer.
fish:
A small support agent refunds an order, emails the customer and closes the ticket, one action every couple of seconds. Press Ctrl-C while it works, then run the same command again from the same folder. The rerun skips the actions that already finished and does the rest. An action you cut off halfway runs again, which is safe because every action carries a stable key. At the end the demo counts what landed in its outbox (one line per action), checks every wake against the journal, and tells you where the run is in the dashboard. Open the run you killed and press Check under Proof of what ran.
--fresh starts a new run. --kill-after 1 kills it for you if you'd rather not race the keyboard. The source is adapters/typescript/cli.ts.
Crash-test any agent (5 minutes)
crash-test/ is a small open tool that kills an agent at each tool call, restarts it, and reports which actions ran twice. It works on agents built on any framework, with or without Argentic, and needs no keys. Start with the quickstart.
Claude Code
Claude Code asks for your model key (optional, only needed to wake agents) and stores it securely. Then run /mcp and sign in to argentic.
MCP only, no plugin:
Then run /mcp to sign in.
claude.ai and Claude Projects
Customize, Connectors, Add custom connector, URL https://getargentic.com/mcp. Under Request headers add x-api-key with your model key (only needed to wake agents). Claude only sends header names Anthropic has approved, and X-Model-Key is not one, so use x-api-key: Argentic reads it as the model key. Request headers is a beta that not every account has yet; if you don't see it, the connector still signs in and reads, and you wake agents from Claude Code or Codex. Sign in and pick your organization. Disconnect any time in your Argentic settings.
For the skills: Customize, Plugins, the + next to Personal plugins, Add marketplace, From a repository, Argentic-Labs-AI/argentic-plugins.
Cursor
Once the listing is live, search for Argentic in the Cursor marketplace. Until then, add the MCP by hand in ~/.cursor/mcp.json:
Cursor opens the sign-in when you enable the server.
Codex
That adds the skills. Add the MCP to ~/.codex/config.toml:
Export MODEL_KEY where Codex starts, then sign in with codex mcp login argentic.
Without the MCP
The HTTP API still works on its own: POST /v1/agents/{agent}/wake and the other routes take an API key (aek_..., created by the create_api_key tool or in the dashboard) as Authorization: Bearer, plus X-Model-Key to wake. See the docs.
Bring your own framework
Already have tools written for the Vercel AI SDK, Mastra, LangChain / LangGraph, Pydantic AI or the OpenAI Agents SDK? Hand the loop to Argentic and keep the tools. adapters/ has one small adapter per framework (TypeScript: npm i @argentic-labs/client; Python: argentic-labs, coming to PyPI, until then pip install it from this repo as adapters/python describes), and examples/ has a runnable refund agent for each, plus one with no framework at all. Kill it mid-run and it resumes without repeating a finished action. Both clients also ship the same demo to try it with nothing to write: npx @argentic-labs/client demo or python -m argentic_labs demo.
Ask your agent to do it
What is in the plugin
argenticskill: how to build on the API without wasting money or claiming features that do not exist.argentic-setupskill: connect, and make a first call for a few cents at most.argentic-quickstartskill: add Argentic to your own project, with keys in.env, and run one small test call.argentic-statusskill: list your agents and which runs got cut off. Read only.argentic-fixskill: find why a run stopped, then resume it or ask you to approve.argenticMCP server, signed in with your Argentic account.- Account tools:
get_account,list_api_keys,create_api_key,revoke_api_key,get_usage,set_budget. - Agent tools:
argentic_wake,argentic_fire_due,argentic_resume,argentic_wakes,argentic_wake_get,argentic_replay,argentic_due,argentic_agents,argentic_approvals,argentic_answer_approval. argentic_answer_approvalneeds an owner or admin. Other tools work as far as your role allows.
- Account tools:
MIT licensed.
Source: README.md at commit 93e3407
Tools
0Version history
2- v0.3.2LatestNov 1, 2026
- v0.3.1Nov 1, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts