NeoPlugin turns the Claude you already pay for into the front door of a team that delivers — campaigns, content, research, publishing — while you talk to one single agent.
Runs on your own machine, with your own Anthropic account (BYO)
Claude is brilliant at answering. It stops when the work starts — the campaign still needs launching, the post still needs publishing, the report still needs to leave the chat.
Neo is the difference: you say what you want, in your own words, and it comes back done. Behind the scenes a specialist takes the task — paid media, social, content, sales, commerce — does the work with your own connectors, and reports back to you through Neo. You never manage the team. You talk to one agent.
|
Without Neo
|
With Neo
|
The door — not the workshop.
This plugin is what puts Neo inside the Claude app and claude.ai: the neo skill and the
neogo MCP connector, over OAuth 2.1 + PKCE. The actual work runs somewhere else: in your
own container, with your own Anthropic account, reached through the terminal in your
dashboard.
| You type | What happens |
|---|---|
/neo |
Talk to Neo — about NeoGo, your account, your connection, your installation |
/neo-login-code |
Hands over the second-factor code to finish signing in to the dashboard |
/neo-link-install |
Hands over the install command for your machine |
Everything you ask NeoGo to do happens in your own Neo, through the dashboard terminal — not here. This plugin installs nothing in it: the two are separate, and each one comes with what it needs.
|
You will need
|
Technical details — connector, tools and repository structure
mcp.neogo.app, over OAuth 2.1 + PKCE. Claude handles the flow transparently — there is no
manual token setup.
| Tool | Description |
|---|---|
get_install_link |
Onboarding — the installer for your OS |
get_plugin_manifest |
Onboarding — what is available |
get_login_code |
The second factor of the login, delivered inside Claude |
These are the tools of the door: connect, subscribe, sign in, install.
NeoPlugin/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest
├── .mcp.json # One connector: neogo (mcp.neogo.app)
├── skills/
│ ├── neo/ # Neo: connects, presents, supports, delegates
│ ├── neo-login-code/ # Shortcut: the second-factor code
│ └── neo-link-install/ # Shortcut: the install command
├── scripts/
│ └── commit.sh # Versioned commit helper
├── LICENSE
└── VERSION
./scripts/commit.sh feat "add new capability"
./scripts/commit.sh major "breaking restructure"
./scripts/commit.sh docs "update readme"Changelog
Kept by hand —
commit.shbumpsVERSIONandplugin.json, but does not touch this section.
- Two new action skills:
/neo-login-code(the second-factor code) and/neo-link-install(the install command). Each one calls the right tool and hands back the result, without going through a conversation. - Why the
neo-prefix: the skill name is what the user types, and the menu filters by text — with the prefix, typing/neolists all three and they choose between talking to Neo and asking for the action. (:is not accepted in a skill name: the spec allows only lowercase letters, digits and hyphens.)
- The plugin belongs to claude.ai — app and web. That is where it serves: the front door to NeoGo, where the user meets it, subscribes and manages the account. The work stays in the container, reached through the dashboard terminal.
- Only the essential stays: the
neoskill and theneogoconnector. The third-party connector pack (composio,kairogen,higgsfield,facebook-ads,metricool,wix,okx,alpaca) leaves.mcp.json: those connectors belong to the user's working environment, which already comes served with them. - README and skill without the old world: the
git cloneinstall and the Remote Control mention are gone — the way to the user's Neo is the dashboard terminal.
- Lowercase identifiers, by spec.
plugin.json'snamerequires kebab-case and a skill'snameallows only lowercase letters, digits and hyphens (official plugin and Agent Skills docs). The values became: pluginneoplugin· skill folderneo· skillnameneo. The user still sees "Neo" — that comes from the persona inSKILL.md, not from the identifier.
- Fix: the plugin described a way of working inherited from the previous version, in which it ran the tasks itself. That is not how it works: the user commands their own Neo directly. Enter the redirection rule — requests for work go where the user's Neo is.
- Renames the
neogoskillskill toneo, matching the name the architecture already used.
- The plugin now carries the external Neo — a persona of its own, born knowing who it is.
- Role made explicit: Neo is the front door. It introduces NeoGo to whoever is not a user yet, and is the point of contact for whoever already is (connection, account, installation).
- The plugin has tone, not method. What NeoGo knows how to do does not live here.
- Connector pack in
.mcp.json: besidesneogo(the gateway), 8 third-party connectors —composio,kairogen,higgsfield,facebook-ads,metricool,wix,okx,alpaca— covering the use cases. All remote (type: url). - Lazy auth: connectors are registered but none authenticates on its own — each waits for
authorization until the user wants it;
neogois the first to be authorized.
SKILL.md: vocabulary tuned to match the words the user sees.
SKILL.md: the assistant becomes Neo, instead of merely calling tools.
- README: adds
LICENSEto the structure diagram, plus a note that the changelog is kept by hand (commit.shdoes not edit this section).
- Initial release. Thin gateway: a single
neoentry point plus the MCP connector (OAuth 2.1 + PKCE) tomcp.neogo.app. - What NeoGo knows how to do is served on demand — the plugin stays tiny and always current.
Neo works for you.