Foam Observability

io.github.foam-aiPublished by GitHub account foam-aiv1.0.0Updated Oct 24, 2026

Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Lets an AI assistant query application logs, traces, and metrics from Foam through a remote MCP endpoint.

What you can do
Foam Observability is a remote MCP server that connects an AI coding assistant to Foam's observability data. According to the registry description, it lets the assistant query application logs, traces, and metrics. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Useful when you want an assistant to look at your application's logs, traces, or metrics while debugging or investigating behavior, without leaving the coding workflow. It is a fit for teams already sending telemetry to Foam.
Requirements
A remote streamable HTTP endpoint at the provider's API host; no local package or runtime is declared. A Foam account and a bearer token sent in the Authorization header are required. Network access to the endpoint is needed.
Before you install
The server requires a bearer token in the Authorization header, which is a credential; keep it private and scope it as narrowly as your Foam account allows. The manifest gives no detail on what the tools read or change, so review the provider's documentation before connecting.

Installation

In SourceWeft

  1. Open Foam Observability in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.foam-ai%2Fobservability/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "foam-observability": {
      "type": "http",
      "url": "https://sdk.api.foam.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

39% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.