/v1/chat/completions
# Export graph data
poetry run terravision graphdata --source --outfile architecture.tvg.json
# Run as an MCPserver for AI agents (needs the optional [mcp] extra)
poetry run terravision mcp --output
pair with calls by INDEX. Per-tool headlines are a LIST, not a rule; MCP `server__tool` shows as `server/tool` via `MCPManager.parseNamespacedName`. Guards: `ToolCallDisplayTests`, `ChatRowBuilderTests`.
- **A background handle
recorded as `command.executed`, carry Python status/output metadata, and have no invented exit code. MCP is not separately attributed because Prime exposes integrations inside the kernel. `beacon endpoint prime sync
coding assistants (Claude, Cursor, Copilot, etc.) working in this repo.
## What this is
MCPserver that connects Google Search Console to AI assistants.
Single file: `gsc_server.py` (~1,670 lines). Built
Gateway** - a CLI plugin that enables easy and secure running of Model Context Protocol (MCP) servers through Docker containers. The plugin acts as a gateway between AI clients and containerized
host directories into Docker example containers.
- If an example needs tools, skills, or MCPservers, install them inside the container during setup.
## Testing Examples (ACP v2)
Examples should be validated
changes, restart the backend container: `just foundry-dev-down && just foundry-dev`.
- The dev server has debug logging enabled by default (`RIVET_LOG_LEVEL=debug`, `FOUNDRY_LOG_LEVEL=debug
current project's config (enables its scripts and copy_files)
./target/release/agtx trust
# Run the MCPserver (global mode, or project-scoped with a path)
./target/release/agtx mcp-serve [path]
# Serve
commit hooks)
pre-commit run --all-files
```
### Frontend (React/TypeScript)
```bash
cd frontend
# Start development server (proxies to Django on :8000)
yarn start
# Run unit tests (Vitest) - watches by default
yarn
validated self-evolution engine, communicates via Slack/Web Chat/Telegram/Email/Webhook, and exposes all capabilities as an MCPserver. 30,000+ lines of TypeScript, 1,819 tests, v0.20.2. Apache 2.0, repo at ghostwright/phantom
workers/` | Thin. Routers shape HTTP; tasks dispatch into a service. `api/mcp_server.py` mounts an MCPserver at `/mcp` whose tools call those routers in-process over an ASGI transport (forwarding
multi-language client SDKs and plugins (AIP identity + Prismer Cloud platform families).
> **Note:** The server backend is closed-source and is **not** included in this public repository. This repo
coding agent
(Claude Code, Codex, OpenCode, Cursor), this CLI for manual access, and the
MCPserver (`haft serve`) for programmatic access.
Standalone interactive agent (`haft agent`), TUI, and desktop wrappers
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.