Add basic build/deploy pipeline
This commit is contained in:
27
README.md
27
README.md
@@ -2,7 +2,7 @@
|
||||
|
||||
Meta MCP is a ContextVM server that accepts **requirements** for new MCP tools and returns a job id. It is intended to be used by other AIs that only have access to a single "meta" tool. The meta MCP then builds, deploys, and announces a new MCP server via Nostr (ContextVM).
|
||||
|
||||
This repo contains the **server-side** MCP for the meta tool. It currently implements the request + job tracking surface; the build pipeline is stubbed and will be wired to the ContextVM/CVMI deployment flow next.
|
||||
This repo contains the **server-side** MCP for the meta tool. It implements the request + job tracking surface and a simple build/deploy pipeline (scaffold → build → announce via CVMI).
|
||||
|
||||
---
|
||||
|
||||
@@ -86,12 +86,31 @@ You can set `CVMI_SERVE_*` env vars to configure relays, encryption, and keys.
|
||||
|
||||
---
|
||||
|
||||
## Pipeline
|
||||
|
||||
The pipeline is currently minimal and runs locally:
|
||||
|
||||
1) Scaffold a new MCP server in `outputDir`
|
||||
2) `npm install` + `npm run build`
|
||||
3) Run `npx cvmi serve -- node dist/server.js`
|
||||
4) Parse and store the announced pubkey
|
||||
|
||||
Configuration is read from `/root/.meta-mcp/config.json` (or `META_MCP_CONFIG`).
|
||||
|
||||
Example config:
|
||||
```json
|
||||
{
|
||||
"outputDir": "/root/.openclaw/workspace/generated",
|
||||
"cvmi": { "seedPath": "/root/.cvmi/seed.json" }
|
||||
}
|
||||
```
|
||||
|
||||
## Next Steps
|
||||
|
||||
- Wire this server to a build/deploy pipeline
|
||||
- Add persistent storage for job state
|
||||
- Auto-create repos + scaffolds for new MCPs
|
||||
- Auto-start new MCP servers and announce via CVMI
|
||||
- Repo creation + git push for generated MCPs
|
||||
- Systemd services per generated MCP
|
||||
- Security controls / rate limits
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user