
agent-exporter MCP bridge
io.github.xiaojiou176-openPublished by GitHub account xiaojiou176-openv0.1.2Updated Oct 28, 2026
Local stdio MCP bridge for archive publishing, retrieval, and governance evidence.
Overview
Local stdio MCP bridge for publishing, retrieving and governing agent configuration archives exported by the AgentExport workbench.
- What you can do
- Publish agent configuration archives to a destination
- Retrieve archived agent configuration
- Provide governance evidence about exports
- Bridge the AgentExport export workbench to an MCP client over local stdio
- When to use it
- Useful if you already work with AgentExport and want an assistant to publish or pull back exported agent setups (skills, prompts, tools, modes) and check governance evidence, rather than doing it by hand.
- Requirements
- Runs as a local process on the user's machine over stdio; desktop only, not web-executable. No packages, environment variables, headers or authentication are declared. The README describes installing the AgentExport workbench from its repository and following per-stack quickstart docs.
Installation
In SourceWeft
- Open agent-exporter MCP bridge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AgentExport
beam your agent config to any planet
[Stars] [Last Commit] [License]
What You Get • Install • How It Work • Ecosystem
AgentExport is a Rust workbench that exports your agent setup — skills, prompts, tools, modes — to every coding-agent surface in one shot. Configure once. Beam everywhere.
One config, many agents. One beam, many platforms.
What You Get
[!IMPORTANT] Local-first by default. No silent telemetry. No cloud round-trip. Your data stays on your machine until you explicitly ship it somewhere.
Install
Three commands. No curl | sh. No login. Read what you run.
Install break? Open your favorite agent and say "Read AGENTS.md and bootstrap AgentExport for me." Agent fix own brain. Long version: docs/.
How It Work
The repo is seven layers — exactly the seven commits in git log. New work goes in as small named PRs. No 50-file mystery commits.
git log reads like a building floor plan. Look once, know the whole shape.
Ecosystem
AgentExport lives in the *Me family: three personal tools. command-style names, stupid-simple jobs.
Cross-family taste: AgentExport · BrewMe · OpenVibeCoding · proofyard.
Star This Repo
If AgentExport saves you a click, an hour, or a headache — star costs zero. Fair trade. ⭐
Also by Yifeng[Terry] Yu
- BrewMe — wake up, news already brewed
- AgentGangGang — five AIs in one sidebar
- OpenVibeCoding — AI codes overnight, you ship in the morning
- proofyard — every claim ships with its receipt
- dealyard — let prices fight, you sit and watch
License
MIT — small print, big freedom.
Source: README.md at commit 0e1a59d
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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