# Telemio MCP workspace companion

Use `https://mcp.telemio.sh/mcp` when a coding agent, chat harness, or automation should work alongside a Telemio workspace while software is being built or maintained.

Create a workspace MCP key from `Console -> MCP`. The key begins with `tmio_mcp_`, is shown in plaintext only when created, and must be stored in the harness secret/environment system rather than committed to source control.

## Workspace boundary

Each MCP key is bound to one workspace. It cannot switch to another workspace by supplying a different workspace header. Create a separate key for another workspace.

MCP keys are control/query credentials, not telemetry ingest credentials. Do not embed them in browser, mobile, desktop, or other distributed client binaries.

## Current tools

The workspace companion can:

- summarize workspace telemetry
- run TQL queries
- list and inspect runtime/session graphs
- list dashboards
- create TQL-backed dashboard visualizations
- discover actionable integration setup paths
- return direct Telemio console links

Integration tools distinguish between setup guidance and user-controlled authorization. An MCP client must not claim an OAuth connection succeeded unless the external provider authorization actually completed.

## Recommended workflow

1. Connect the coding agent or harness to the MCP endpoint.
2. Inspect the repository and existing Telemio workspace before changing instrumentation.
3. Reuse existing OpenTelemetry and detect the real runtime boundaries.
4. Add only missing traces, metrics, logs, runtime identity, product events, or model/tool metadata.
5. Query Telemio through MCP after the change to verify the expected signals arrive.
6. Create or update a focused dashboard when a visualization is useful.
7. Return direct Telemio console links in the implementation report.
8. Reuse the connection later to audit instrumentation drift as the application evolves.

Use the same model for services, workers, mobile apps, browsers, desktop apps, serverless functions, ephemeral compute, workflows, jobs, CLIs, and agent runtimes.

Reference: https://telemio.sh/agent/runtime-sessions.md

## Privacy

Default to metadata-first instrumentation. Do not send prompts, model responses, raw tool payloads, request bodies, page contents, credentials, authorization headers, cookies, tokens, source code, or other sensitive content unless the application has an explicit requirement and suitable controls.