discussion_helper.mcp module

The MCP surface: the same routes, republished as agent tools.

Module summary

There is no second implementation here. discussion_helper.api already describes every operation — its parameters, its types, its operation_id — and fastapi-mcp turns that description into a tool catalogue. An agent starting a session and a shell calling POST /sessions reach the same function, so the two surfaces cannot drift into disagreeing.

What an agent can actually do with a conversation

Not hold one: it has no microphone and no ears. What it has is the other three verbs, and they are the useful ones for an assistant sitting beside a person:

  • start a session on the user’s machine, and end it;

  • watch it — the transcript as it grows, the floor, and where each exchange’s latency went;

  • interrupt it, which is the one that matters. “Stop talking” is a thing people say to an agent, and routing it through the same Voice.stop the microphone’s barge-in uses means it stops the same way: discarding what was synthesised rather than letting it drain.

  • take one turn as text, which is the only way an agent can ask the conversation’s model something directly.

Author

Warith HARCHAOUI — https://linkedin.com/in/warith-harchaoui/

discussion_helper.mcp.main(argv=None)[source]

Serve the API with its MCP endpoint mounted.

Returns:

A process exit code. Non-zero when the extra is missing, with the install line rather than a traceback about a module the reader has never imported.

Return type:

int

Parameters:

argv (list[str] | None)