List your agent

Autopo

MCP server · hosted · installable · v0.6.3 · io.github.autopoiesis-ai/mcp
Online · tested 2h agoNEW · 3d agoNew version 3h agoSeen in the registry 2h ago

Run your AI-run company from Claude Code, Codex, Cursor or ChatGPT: inbox, tasks, team, Studio.

What it does

Autopo is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installYES
Version0.6.3
Packagesnpm
PriceNot in the registry
First seen02 Nov 2026
Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

  • https://autopoiesis-mcp-267405155162.us-west1.run.app/mcp streamable-http

Install package

  • NPM @autopo/mcp v0.6.3 · runs locally (stdio)

Required: Authorization, AUTOPOIESIS_TOKEN (get them from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "autopo": {
      "url": "https://autopoiesis-mcp-267405155162.us-west1.run.app/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE Autopo answered an MCP connection on 05 Nov 2026 and introduced itself as autopoiesis 0.6.3 (MCP protocol 2025-06-18).

99 tools offered to AI assistants

  • list_companies · The companies you belong to (id, name, stage, kind). Other tools take `company`: one of these ids. Start here.
  • whoami · The signed-in person: name, email, preferences, and how many companies they are in.
  • founder_home · What needs you, what improved and what is stuck in a company right now: the home screen's digest, the open decisions, running work, delivered work and your requests. Start here for 'what happened'.
  • company_overview · The company: its charter, stage, team, budget and gates.
  • activity · The company's activity feed, newest first (who did what, when). `after`: only events after this ISO time.
  • list_briefings · The CEO's board briefings (spoken updates), newest first, with their text.
  • get_briefing · One briefing: its sections, the decisions it asked for, and what was said.
  • brief_me_now · Ask the CEO for a fresh briefing since your last one (at most 3 a day). It is written and voiced in the background: read it with get_briefing in a minute.
  • list_decisions · The Board inbox: cards waiting for you (`status` pending, default), or decided ones. Each card says what the team wants, why, the risk tier and the amount; decide with `decide`.
  • get_decision · One inbox card in full: the ask, the agent's case, the options, the work behind it.
  • decide · Decide an inbox card as the founder: approve, reject (a `note` is required) or cancel. For a question card, `answer` is the chosen option's value. `edited_input` approves with a change to what was asked. You are asked to confirm in a dialog
  • comment_on_decision · Ask the team something about a card before deciding; the requesting agent answers.
Show 87 more
  • list_tasks · The work board: tasks by status, assignee role or goal; `q` searches titles; `mine: true` only what you asked for (your requests).
  • get_task · One task in full: description, criteria, status, the thread's last comments, its pull requests and deliverables.
  • create_task · Give the team work, or make a request of your own (the CEO routes it when no assignee is named): a title, what done looks like, criteria. `assignee` is an agent id (list_agents).
  • update_task · Change a task: its title, description, status, priority, assignee or criteria. To cancel one, use cancel_task.
  • comment_on_task · Write in a task's thread as the founder: the assignee reads it and answers (a comment wakes them).
  • cancel_task · Cancel a task (and its open subtasks, pending cards and live runs). `preview: true` only says what it would take. You confirm in a dialog before it is final.
  • list_agents · The team: every agent with its role, title, state and whether it is on. Chat with one through ask_agent.
  • ask_agent · Start a chat with an agent (list_agents) and wait for the answer. `agent` is the agent's id or role key (ceo, cto, creative…). Beside the Studio, pass `production` (a video id) so the Creative Director sees that video. The reply's `actions`
  • continue_chat · Send another message in an existing chat and wait for the reply.
  • read_chat · A chat's messages, oldest first (the last reply's status says whether it is still answering).
  • list_chats · Your chats across the team (pinned first, then recent); `q` searches titles and content.
  • apply_chat_action · Apply a proposal an agent made in a chat (a task, a note, media to make, a card): the action's id from the reply's `actions`. `edits` changes fields of its payload first. `dismiss: true` declines it. Applying can start work or spend credits
  • list_runs · Agent runs: `status` active (queued, running), finished, or a comma list; `agent` an agent id.
  • get_run · One run: its status, cost, and its events (tool calls, text) from `after_seq`.
  • nudge_run · Steer a run that is still going: a line of guidance the agent reads at its next step.
  • list_artifacts · What the team made: documents, research, decks, tables, videos, designs (`type`), delivered work, `q` searches, `starred` only yours.
  • get_artifact · One artifact in full (its body, content, version, who made it), with `app_url`: its page in the web app.
  • artifact_feedback · Ask for a revision of an artifact: a task for the agent who made it; the change lands as a new version.
  • studio_overview · The Studio: every model this company can run (what it is for, price, shapes, availability), the voices, the default models and narrator, providers, the team's allowance, and whether this server can check and render code films (`can_render_c
  • studio_settings · Change the Studio's defaults: `default_models` by kind (image, video, voice, music: model keys from studio_overview) and the default narrator `voice` (a voice key).
  • list_media · The media library: images, clips, voice lines and music, with filters (`kind` image|video|audio, `source` generated|uploaded|recorded|rendered, `q`, `starred`).
  • get_media · One piece of media: its prompt, model, settings, link and state.
  • generate_media · Make an image, a clip, a voice line or music in the Studio (spends credits; you confirm the cost in a dialog): `kind`, a `prompt`, optionally a `model` (studio_overview), `aspect_ratio`, `duration` (seconds, clips), `count` (images), `voice
  • list_videos · The Studio's videos (productions): title, status, shape, length.
  • get_video · A video's storyboard in full: every shot (picture, line, text, seconds, direction, takes), the style and models it is made with, the presenter, cards, the finished render, and what is missing before it can render. `engine` says how it is cu
  • create_video · Start a video: a title, the brief (who it's for, what it must show, the one thing to feel), the shape (16:9, 9:16, 1:1, 4:5) and the length in seconds. The platform drafts the storyboard from the brief (a little model time, billed like an a
  • set_video_shots · Replace a video's storyboard: shots in order, each {visual: generate|footage|title|presenter, prompt, voiceover, on_screen_text, duration_seconds, media?, voice?, direction?, keep_audio?, notes?}. Send a shot's `id` to keep its media; a sho
  • upload_media · Put your own files into the Studio library: recordings, screen captures, photos, a voice track, music. Each item is a `path` on the machine this server runs on (a file, or a folder: every image, clip and audio file in it, in name order; you
  • attach_media · Put a library item on one shot: `media` (an image or clip: the shot's picture, as footage) or `voice` (an audio item: the shot's line). The other shots stay as they are. `keep_audio: true` keeps the clip's own sound under the voice-over.
  • update_video · Change a video: title, brief, shape, or its `style`: music, captions, transition (cut|fade), colours, the narrator `voice`, the `look` (palette, light, camera, texture, mood, type, avoid, brand light|balanced|strong), the music cue (`music_
  • make_video_media · Make what a video still lacks (spends credits; you confirm the cost in a dialog): `what` all (clips and voice lines), visuals, voice, or music (composed from the style’s music cue). `model` overrides the clip model for this call. Then wait_
  • video_keyframes · Make the keyframes first (a still of each generate shot’s first frame, cents each; you confirm in a dialog) so the look is locked before clips are paid for. `shots`: shot ids, default every shot without one.
  • critique_video · The critic judges the latest generated takes (`stage` keyframes or clips) against each shot’s direction and puts the best on the shot. `stage` cut is the audience review of the render, for any film, generated or not: the viewer it is made f
  • wait_for_video · Wait while a video’s media or render is being made (up to `wait_seconds`, default 60, max 120) and return where it stands: shots generating, the render, what is still missing. Call it again if it is still going.
  • render_video · Cut the video into one MP4 (free). get_video says what is missing when it refuses; the render takes a minute or two: wait_for_video. A code film (`engine` remotion) renders its last checked version through Remotion, so the check must pass f
  • design_video_cards · Make (or re-sync) the cards drawn over a video’s shots, one scene per shot, editable in the Studio’s design editor. `remove: true` takes them off (you confirm in a dialog).
  • video_plan · A video as a plan (JSON): its shots, presenter, style, media ids. Change it and import it back with import_video_plan.
  • import_video_plan · A whole video at once from a plan (the shape video_plan returns: title, brief, aspect_ratio, style, presenter, shots). Give the `plan` as JSON, or a `path` on this machine (a zip with plan.json and the files it names as file:…, a plan.json
  • export_video · A link to a zip of the video’s plan and every file it names (works for a week).
  • delete_video · Delete a video (its media stay in the library). You confirm in a dialog.
  • update_media · Rename, star or delete a piece of media; `retry` makes a failed generation again (it spends credits again: you confirm in a dialog); `cancel` stops one.
  • convert_video_to_code · Override how a video is cut: the Creative Director picks per film (`cut_choice` on get_video), so call this only when the person asks for a code film, and leave a film she chose alone otherwise. Its storyboard compiles to a Remotion project
  • get_video_code · A video's code film (a Remotion project its storyboard compiles to): the version, the head's files (paths), the scenes, the last check (ok, errors with file and line, warnings), the preview link and the latest versions. With `file` (a path,
  • write_video_code · Write files of a video's code film: `files` [{path, content}] (content null removes a file; paths under src/ ending .ts, .tsx, .js, .jsx, .css or .json; src/film.json, package.json and tsconfig.json are the compiler's and follow the storybo
  • check_video_code · Check a video's code film again without changing it: tsc, the lint, the scene list and the preview bundle run on the head. `check` has ok, errors (file, line, shot, message), warnings (craft: a card over 7 words, no hook by 2 s…) and the ru
  • video_frames · Draw stills of a video's code film as Studio images (free; seconds after the first build): `frames` (frame numbers at the film's fps) or `every_seconds`; neither: the middle of every shot. Up to 12 a call. Needs a passing check. Each result
  • video_code_versions · Every version of a video's code film, newest first: number, source (compiler, agent, founder, restore), note, files, who made it and when; `head` is the current one.
  • restore_video_code · Bring an earlier version of a video's code film back as a new version (source restore), checked at once.
  • plan · The workspace’s plan: run-minutes used and left this period, the plans on offer, how each model and media provider is paid (your own key, or Autopo’s billed to the card daily), today’s unbilled use and the recent daily charges. `enabled: fa
  • change_plan · Move the workspace to another plan (free, starter, pro, max). From free or legacy it opens a Stripe checkout in your browser (nothing is charged until you pay there); between paid plans it changes at once and invoices the difference now, so
  • plan_settings · Change how the plan may spend: `overage_cap_cents` (Max only: the most overage a period may run up, 0–10,000,000) and `disabled_providers` (every model or media provider to turn off, on your key and Autopo’s alike; `[]` turns all back on).
  • billing_page · Open a Stripe page in your browser: `card` saves a card for daily billing of Autopo’s keys (nothing is bought), `portal` is the customer portal (card, invoices, cancelling).
  • create_artifact · Add your own artifact to the company’s documents, made by you (agents read it as material, not instructions): exactly one of `markdown`, `html`, `media_ids`, `upload_id` or `type` + `content`. `use_as_context` (default true) lets the team r
  • revise_artifact · A new version of an artifact a member made (agents’ work is revised with artifact_feedback): the same kinds of input as create_artifact, or `content` alone; it keeps its type. `base_version` guards against overwriting someone else’s newer v
  • artifact_links · The public links an artifact has been shared by, newest first: the address, the version it shows, views, expiry, revoked.
  • share_artifact · Make a public link to an artifact that anyone with the address can open without signing in (review notes, costs and hidden parts never show). `version` pins it (else it follows the latest), `scope` view_history also shows past versions, `ex
  • unshare_artifact · Revoke a public link to an artifact (`link` is its token from artifact_links): the address stops opening at once.
  • list_errands · Errands (web chores Peyk does in a browser, stopping before anything you can’t undo): what needs you, the one on it, what is up next, drafts, and the 20 newest finished.
  • get_errand · One errand in full: its plan, its stops (the checkpoints waiting on you, with their ids), its steps and its receipt.
  • draft_errand · Write what you need done on the web (`text`, 3–2000 chars) and Peyk drafts a plan: its sites, steps and the stops where he waits for you. One cheap model call (about 2¢), confirmed in a dialog; nothing runs until start_errand. `agent` picks
  • start_errand · Start a drafted errand: Peyk (or `agent`) works its plan in a browser and stops at every checkpoint for you (answer_errand). Runs cost credits up to the plan’s cap; you confirm the plan in a dialog first.
  • answer_errand · Answer an errand’s stop (its card): `yes` lets that step through (a payment, a submit, a send), `no` stops it, `myself` you do it in the Chrome on your computer, `done` for a hand-off you did. `note` is what you tell Peyk (a reference, a ch
  • errand_sign_in · Before a drafted errand that needs your accounts: `open` opens the site in the Chrome on your paired computer so you sign in yourself (Peyk never types a password); `done` says you are signed in and closes the window. `site` is one of the p
  • list_members · The people in the company (owner, admins, members, viewers) with their user ids and whether they are online.
  • chat_coworkers · Bring a coworker (a person of the company, `user` id from list_members) into a chat with the agents, or take them out (`remove`; leaving is removing yourself). Members read it live, write in it and apply what the agents suggest.
  • competitors · The competitor radar: the rivals watched (and those proposed, waiting for your yes) and what changed on their pages in the last 60 days.
  • manage_competitor · Change the radar: `add` a rival (`name`, `url`, `note`?; up to 8), `confirm` a proposed one (`competitor`), `remove` one (its history stays), `discover` rivals from a few web searches (proposed for your yes), or `scan` their pages now (once
  • shopify_store · The company’s Shopify store, read-only: whether it is connected, the store, its currency, the webhooks, when it last synced and how many products and orders were read.
  • connect_shopify · Connect the company’s Shopify store (`shop`: its name, myshopify.com domain or admin URL): opens Shopify in your browser to install the Autopo app, which only reads products, orders, inventory and customers.
  • sync_shopify · Read the connected store again now (`check` instead tests that the connection still works and has every permission).
  • brand_brain · The brand brain: what the company says about itself, for whom, against whom, in what voice (every writer reads it).
  • social_accounts · The company’s social accounts and networks, and what each account may post on its own.
  • list_posts · Social posts: upcoming, published or failed (`status`), per `account`.
  • check_posts · Run the pre-publish gate on posts you wrote (nothing is posted): each post’s review against the brand.
  • create_posts · Post as yourself (no card): `posts` [{account, text, media?}], now or at `schedule_at` (ISO). You confirm in a dialog: a post cannot be unpublished from here.
  • marketing_learnings · What worked and what didn’t: the learnings log, newest first.
  • budget · The month’s spend against the budget, by agent and kind, and the credits left.
  • ledger · Every charge, newest first (`kind`, `agent` filter).
  • buy_credits · Open a checkout in your browser to add credits to a company (1 credit = $1). Nothing is charged until you pay there.
  • api_request · Call any endpoint of the Autopo REST API as yourself: `method`, `path` (starts with /api/, ids filled in), optional JSON `body` and `query`. api_reference is the manual: use this for anything the other tools don’t cover. Reads go straight t
  • api_reference · The REST API’s reference (OpenAPI): with no arguments, every endpoint in brief (method, path, summary); `search` narrows by words in the path or summary; `path` (+ `method`) gives one endpoint’s parameters and body.
  • open_in_app · Open a place in the Autopo web app in your browser: `what` is home, hive, inbox, task, work, knowledge, team, chat, studio, video, marketing, social, money, connectors or settings; `id` the card, task, artifact, chat or video when there is
  • app_decide · Decide a card from the inbox view. Hidden from the model: the click is the confirmation.
  • app_refresh_inbox · Reload the pending cards for the inbox view.
  • app_video · Reload a video, or act on it: keyframes, make media, critique, render. The click is the confirmation.
  • app_media · Star, retry or reload media from the gallery view.
  • app_artifact · Reload an artifact with its links, or make its public link. The click is the confirmation.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install package@autopo/mcpDECLAREDSRC-001 Official MCP Registry2h ago
Version0.6.3DECLAREDSRC-001 Official MCP Registry2h ago
Hosted endpointhttps://autopoiesis-mcp-267405155162.us-west1.run.app/mcpDECLAREDSRC-001 Official MCP Registry2h ago
Websitehttps://autopoiesis.appDECLAREDSRC-001 Official MCP Registry2h ago
Package registriesnpmDECLAREDSRC-001 Official MCP Registry2h ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry2h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2h ago

Change history

  • VERSION05 Nov 2026
    0.6.2 → 0.6.3
  • VERSION05 Nov 2026
    0.6.1 → 0.6.2
  • VERSION02 Nov 2026
    0.6.0 → 0.6.1
  • VERSION02 Nov 2026
    0.5.2 → 0.6.0
  • VERSION02 Nov 2026
    0.5.1 → 0.5.2
  • VERSION02 Nov 2026
    0.5.0 → 0.5.1
  • VERSION02 Nov 2026
    0.4.4 → 0.5.0
  • NEW02 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Autopo? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor AutopoLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Autopo?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedInListed on Electra Index
<a href="https://electraindex.com/mcp/autopo?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/autopo" alt="Listed on Electra Index"></a>

Questions about Autopo

How do I connect Autopo?

Use the hosted endpoint https://autopoiesis-mcp-267405155162.us-west1.run.app/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Autopo need an API key or token?

Yes. The registry entry lists required values: Authorization, AUTOPOIESIS_TOKEN. Get them from the publisher.

What tools does Autopo offer?

When Electra Index connected on 05 Nov 2026, it listed 99 tools: list_companies, whoami, founder_home, company_overview, activity, list_briefings, get_briefing, brief_me_now and more. The full list is in "Live check" above.

Is Autopo online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.