The hosted LogBrew MCP server lets an AI agent read telemetry from your LogBrew projects. You do not install it. Add its URL to your MCP client: - Transport: Streamable HTTP. The server accepts MCP protocol versions 2026-07-28, 2025-11-25 and 2025-06-18. - Authorization: OAuth. Your client opens the LogBrew authorization page, you sign in, and you select the projects that the agent can read. The r
npx mdskills install LogBrewCo/logbrewco-mcpRelated
1# LogBrew MCP23The hosted LogBrew MCP server lets an AI agent read telemetry from your4LogBrew projects. You do not install it. Add its URL to your MCP client:56```text7https://mcp.logbrew.co/mcp8```910- **Transport:** Streamable HTTP. The server accepts MCP protocol versions11 `2026-07-28`, `2025-11-25` and `2025-06-18`.12- **Authorization:** OAuth. Your client opens the LogBrew authorization page,13 you sign in, and you select the projects that the agent can read. The `read`14 scope lets the agent read. Operations that change data need the separate15 `write` scope, which you can decline when you approve the connection.16- **Read-only:** The agent cannot change issues, projects or account settings.17 A read of a project that you did not approve returns `permission_denied`.18- **Connection lifetime:** An access token is valid for 1 hour, and the client19 refreshes it while you use the connection. A connection ends after 30 days20 without use, or 90 days after you approved it. Revoke a connection in the21 LogBrew dashboard under Settings > MCP connections, or with22 `logbrew mcp revoke`.2324## What an agent can read2526The server has 2 tools, both annotated read-only:2728| Tool | What it does |29| --- | --- |30| `search` | Finds read operations and returns the contract of one operation: its input and output schemas, permission, cost, safety and stability. |31| `execute` | Runs one operation that `search` found and returns structured data, or an error with a stable code and a next action. |3233The operations read issues (investigation, lists, activity, owners and34ownership rules), logs, traces, spans, metrics, product actions, releases,35signal volume and product analytics. The [operation reference](docs/operations.md)36lists every operation in the shipped catalog and its limits.3738## Supported clients3940Any MCP client that completes LogBrew authorization can connect. The client can41publish a client ID metadata document or register dynamically.4243[Connect an AI agent with MCP](https://docs.logbrew.co/guides/mcp) shows the44setup for many clients. For example, in Claude Code:4546```sh47claude mcp add --transport http logbrew https://mcp.logbrew.co/mcp48claude mcp login logbrew49```5051## Development5253Use Rust 1.99.1, cargo-deny 0.20.2 and Tombi 1.7.2. Run every required gate54from the repository root:5556```sh57scripts/check-all.sh58```5960CI runs the same script. Tests use local HTTPS servers and synthetic61credentials.6263`server.json` describes the hosted server for the MCP Registry. Check it with64`mcp-publisher validate` after you change it.6566The dependency policy in `deny.toml` covers normal, build and test dependencies67across the resolved graph. It checks license requirements and registry sources,68rejects wildcard versions, and constrains reviewed features to exact dependency69versions. Five exact duplicate version exceptions preserve incompatible upstream70APIs; no dependency subtree is excluded. Unused license and source allowances71fail the check, and every warning fails.7273The toolchain file pins rustfmt and Clippy with Rust 1.99.1. The server uses74the official MCP Rust SDK, rmcp 3.5.1, with Axum and Tokio. Cargo.lock records75the resolved dependency graph.7677The operation validator accepts object-rooted JSON, rejects duplicate78keys at every depth, and preserves exact numbers. Limits are 64 nested79containers, 256 characters per number, and decimal exponents from -1024 to801024. Input, output, and schema byte limits apply before parsing. Schemas use81JSON Schema 2020-12 by default with format assertions and no external loading.8283Startup file loading supports Linux and macOS. It requires84operator-managed directories and absolute regular-file paths, checks byte and85permission bounds, and rejects final-component symlinks. Files are opened86without waiting for a FIFO writer and their identity is checked before reading.87The configuration reader accepts a private file up to 16 KiB with88version `"5"` only. Every field is required and must appear exactly once with a89nonempty string value: `listen`, `resource`, `issuer`,90`introspection_endpoint`, `execution_endpoint`, `service_client_id`,91`service_secret_file`, `catalog_file`, `catalog_sha256`, `certificate_file` and92`private_key_file`. The `admission` object is also required (see below). It93rejects unknown fields, case aliases, duplicate decoded keys, invalid UTF-8,94trailing documents, and inline secret fields. It preserves secret-file95references without opening them.9697Two optional fields send request telemetry to a LogBrew project. They must98appear together: `telemetry_endpoint`, the HTTPS ingest URL, and99`telemetry_key_file`, a private file that holds the project's ingest key with100no trailing newline. Each finished request, search, and execution becomes one101span with its duration and a fixed outcome such as `completed`,102`unauthorized`, or `unavailable`. An execution also names its operation, but103only when the catalog contains it. An outcome that this server or the API104caused (`configuration`, `invalid_output`, `unavailable`, or `deadline`) also105opens an issue, such as `mcp execute logs.read.v1 unavailable`. Telemetry never106contains tool arguments, results, tokens, client identity, or error text. At107most 1,024 records wait for delivery, and the server sends at most one request108per second. When the queue is full or a request fails, the server drops those109records and reports how many in its next request. Telemetry never delays or110rejects an MCP request.111112`admission` limits requests that have not proven authority, per client:113114```json115"admission": {"burst": 16, "per_minute": 600, "tracked_clients": 10000,116 "rejected_token_seconds": 30, "trusted_proxy": "127.0.0.1"}117```118119Each MCP request reserves one unit of its client's budget before it takes a120request slot or starts introspection; a request whose token verifies gets the121unit back. A client may start `burst` (1 to 64) unverified requests at once,122refilled at `per_minute` (1 to 60000). Beyond that the server answers HTTP 429123with `Retry-After` in whole seconds and the body124`too many unauthenticated requests`, without introspection. Up to125`tracked_clients` (1 to 100000) clients get their own budget; idle clients are126evicted, and the rest share one overflow budget, so memory stays bounded. IPv6127clients are grouped by /64. The client is the TCP peer, or the single128`X-Real-IP` address when the peer is the optional `trusted_proxy`. A token that129introspection rejected (inactive, invalid or missing scope) is130refused for `rejected_token_seconds` (0 to 300, 0 disables) without asking131again; up to 4096 token digests are kept, never tokens. Unavailable132introspection is never remembered.133134One service login, `service_client_id` with the secret in135`service_secret_file`, authenticates both introspection and execution. The136issuer and API must hold the same pair. `issuer` must equal the authorization137server's issuer identifier byte for byte, and `resource` must equal the audience138the issuer binds into tokens. Startup rejects an issuer that ends with `/`,139because it would deny every request. Introspection alone decides which clients140can connect. The server accepts any client ID that the authorization server141confirms, if it has 1 to 2048 printable ASCII characters. Every request142needs the delegated `read` scope. An operation whose permission is `write`143also needs the separately granted `write` scope. Without it, `execute`144answers HTTP 403 before contacting the API, with an `insufficient_scope`145challenge that asks for `read write`. Scopes are not configurable. The server146publishes RFC 9728 protected resource metadata at147`/.well-known/oauth-protected-resource` followed by the resource path. The148document names the issuer as the only authorization server and lists the149`read` and `write` scopes. The 401 challenge asks for `read` only, and every150401 and 403 challenge links to the document.151152The separate service loader reads referenced material and constructs the153authenticated handler without opening a listener or contacting upstream services.154It requires a numeric IP and nonzero port, verifies the catalog SHA-256, parses155the matching TLS certificate/key pair, and applies service endpoint and credential156validation. File limits are 8 MiB for the catalog, 256 KiB for certificates,15764 KiB for the private key, and 8 KiB per machine secret. Key and secret files158must have no group or other permissions. Secret bytes are used exactly as stored,159without newline trimming. Temporary loaded key/secret buffers are cleared after160assembly; the service retains the credentials it needs.161162The server can run from source with an operator-provided configuration:163164```sh165cargo run --locked -- /absolute/path/to/config.json166```167168It validates startup material before binding the configured address. Outbound169connections use system TLS trust, with no inherited proxy or custom dial hooks.170SIGINT and SIGTERM request graceful shutdown. Startup and serving failures exit171nonzero without printing paths, credentials, or upstream responses. Source builds172identify themselves as `development`. Use `cargo run --locked -- --version` to173check the package version without loading configuration.174175Check the configuration and its referenced files before starting or replacing176a process:177178```sh179cargo run --locked -- --check-config /absolute/path/to/config.json180```181182The check uses the same loader as startup, then exits without binding a listener183or contacting either upstream service. It can run while the server is listening184on the configured address. Exit status 0 means local validation passed; status 1185means it failed. The executable prints no configuration or credential values.186This check does not prove upstream availability, authorization, certificate187renewal or client connectivity. Startup checks the files again when serving.188189Native process tests cover offline startup, both shutdown signals, listener190release, mismatched certificate/key rejection, and stalled connections. The191process admits at most 64 connections, including TLS negotiation, and closes192excess connections without queueing them. TLS negotiation and HTTP/1 header193reading each have a five-second deadline. Authenticated requests have a194ten-second deadline; graceful shutdown waits up to twelve seconds. An incomplete195drain exits nonzero.196197Local HTTPS tests cover pending execution198cancellation, current-request authorization, revocation, and response boundaries.199The standalone process and HTTPS regression tests share the same serving code.200Tests verify that graceful shutdown closes the listener before active execution201finishes, preserves the complete response, and releases the connection. Cancelling202the serving future closes active requests and stops their upstream work. Request203capacity recovers after cancellation without starting excess introspection work.204205Current-version request tests require protocol version and client capabilities206on each request. Client identity is optional. Missing or mismatched routing207headers receive HTTP 400 with a `HeaderMismatch` error. Unsupported versions208receive the supported-version list; unknown methods receive HTTP 404 with a209JSON-RPC method error. Client response messages, batches, and invalid request IDs210are rejected before execution.211Handler validation errors use HTTP 200 with a JSON-RPC error response. Missing212required request metadata remains an HTTP 400 error.213214The server accepts MCP `2026-07-28`, `2025-11-25`, and `2025-06-18`. A client215on `2025-11-25` or `2025-06-18` starts with `initialize` and then sends the216negotiated version in the `MCP-Protocol-Version` header. The server answers217these clients without sessions: it returns no `Mcp-Session-Id`, and every218request carries its own bearer token and gets the same authorization as a219`2026-07-28` request. Versions before `2025-06-18` are not supported, because220they have no OAuth resource indicator and no structured tool results.221222Content negotiation parses complete media types, accepts case variants and223repeated Accept fields, and requires both JSON and event-stream support with224positive quality values. Current-version GET and DELETE requests receive HTTP225405. Incoming legacy session and event IDs are ignored without creating sessions.226An actual TLS HTTP/2 test covers configured authority, authorization, header227validation, complete results, and cancellation.228229Introspected `iat` and `nbf` times may lead the local clock by up to 60230seconds; a later time is rejected. Authorization tests reject expired credentials, mismatched issuer or audience,231missing required scopes, invalid identity references, and incomplete or malformed232introspection responses before execution. Oversized introspection bodies and233headers and unexpected media types also fail closed. Synthetic HTTPS fixtures234verify one service login and OAuth component encoding at both upstream235endpoints.236237The request router requires the configured resource host, including its port,238on every request. A supplied Origin must be the single configured HTTPS origin;239empty, null, duplicate, foreign, or different-scheme origins are rejected even240for metadata reads. Forwarded headers do not change either check. The SDK's241loopback-host heuristic is replaced by this configured-host check so a loopback242proxy hop can preserve the public host. Browser cross-site protection remains243enabled.244245`catalog/operations.json` is the operation catalog the hosted server loads. The246LogBrew API generates it from the request and response types of its public247read endpoints; this repository ships the generated file unchanged.248`catalog/operations.json.sha256` pins its SHA-256 digest in `sha256sum` format.249Deployments set `catalog_sha256` to that digest, and a test fails if the file,250the pin, and the operation reference in `docs/operations.md` disagree. To251update the catalog, replace both files in one change and update the reference.252253The catalog loader accepts format version 1 and requires an expected254SHA-256 digest from trusted release configuration. It rejects files above 8 MiB,255duplicate keys, unknown metadata fields, unsupported formats, invalid operation256contracts, and any permission other than `read` or `write`. A `read` operation257must be `read_only`. A `write` operation must declare `safety: write`, a title,258and hints that are not read-only. `search` is always read-only. `execute` is259read-only unless the catalog has a write operation; then it declares260`readOnlyHint: false`, and `destructiveHint: true` if any operation may delete261data. Loading a catalog does not grant access to its operations.262263The tools return a `data`/`error` envelope with catalog provenance.264Operation input is limited to 4 KiB and output data to 2 MiB. Envelope metadata265has a separate bounded allowance so it does not consume the operation's budget.266Local HTTPS tests verify complete maximum-size results in both structured JSON267and text content, and rejection of output one byte over its limit.268`provenance.definition_sha256` identifies the sorted serialized operation269definitions used for discovery or execution. It is not the raw catalog-file270digest, a deployment receipt, or proof that returned telemetry is current.271Provenance is null when a request fails before catalog handling or a result272cannot be encoded within its limit. Raw artifact integrity remains a separate273startup check against the configured SHA-256.274275Both tools advertise the same result schema. It distinguishes successful data276from errors, requires valid catalog provenance for success, and constrains error277codes, matching recovery actions, and retry delays. Local tests validate that278schema and reject inconsistent envelopes.279280Errors include `code`,281`next_action`, and `retry_after_ms`. Invalid input points to the input contract;282invalid service output is a separate error and does not return the rejected283data. An unknown retry delay is `null`, distinct from zero. The server does not284retry an operation automatically. An unavailable result asks callers to check285operation status before repeating a potentially state-changing request.286
Full transparency — inspect the skill content before installing.