Start with ask_meshh
MCP is the protocol adapter for external clients, not the product contract itself. Use ask_meshh from Claude, Codex, ChatGPT, and similar clients, then continue threads or check status through Meshh references.
Use MCP to connect Claude, ChatGPT, Codex, and similar external clients to MESHH as a Japan macro research agent.
https://meshh.ai/mcp
MCP is the protocol adapter for external clients, not the product contract itself. Use ask_meshh from Claude, Codex, ChatGPT, and similar clients, then continue threads or check status through Meshh references.
MESHH MCP exposes ask_meshh, continue_meshh_thread, and get_meshh_status. Search, retrieval, diffing, and citation work are internal choices made by the Meshh agent.
The first-party Meshh TUI uses /api/v1/tui with device authorization and destination bearer tokens. It is not configured as an MCP client.
Connect MESHH into Claude's MCP flow and ask a Japan macro research agent directly inside conversations.
Open the ChatGPT and Codex MCP setup flow for MESHH and attach the same agent gateway to your workspace.
Ask Meshh a source-grounded Japan macro research question. Meshh chooses the internal corpus, agent, citation, and source-access tools needed to answer.
Continue an existing Meshh research thread with a follow-up question. Meshh preserves the durable thread and chooses internal tools as needed.
Read product-safe status for a Meshh research thread without exposing RLM runtime internals.
| Tool | Purpose | Required input | Returns |
|---|---|---|---|
ask_meshh |
Ask Meshh a source-grounded Japan macro research question. Meshh chooses the internal corpus, agent, citation, and source-access tools needed to answer. | `question` | answer, thread, and status |
continue_meshh_thread |
Continue an existing Meshh research thread with a follow-up question. Meshh preserves the durable thread and chooses internal tools as needed. | `thread_reference`, `question` | continued answer and references |
get_meshh_status |
Read product-safe status for a Meshh research thread without exposing RLM runtime internals. | `thread_reference` | product-safe thread status |