Skip to content

Reworked technical/tool.md adding MCP support #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cableman merged 1 commit into from
Jul 16, 2026
Merged

Reworked technical/tool.md adding MCP support #57

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions technical/agentic_tool.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1037,6 +1037,15 @@ inside the fallback return empty results, not 500s.
From inside a container on the `app` network: `AGENT_API_BASE_URL=http://litellm:4000/v1`. From outside (e.g. `task` on
the host, or a non-stack environment): `https://litellm.itkdev.dk/v1`.

### 8.7 Exposing the agent over MCP

Once the agent works over HTTP, you can additionally expose it as a **Model Context Protocol tool** so MCP-native
clients (Open WebUI, Claude Desktop) can call it directly — the same capability, a second transport. The move is to
factor the request handling into one service function and have *both* the `POST /search` route and the MCP tool call
it, so their behaviour can't drift. The MCP-specific wiring — mounting FastMCP alongside these routes, the
session-manager lifespan, the pure-ASGI bearer guard, and host validation — lives in the
[Build a tool guide](./tool.md). Reuse the same constant-time `token_matches` from §7.8 across both transports.

## 9. Production - docker compose sever

In production, the agent is **not built from source**.
Expand Down
Loading