Fixter

dev.fixterPublished by fixter.devOfficial publisherv1.0.0Updated Oct 24, 2026

Monitoring for small teams. Logs, traces, metrics, live issue tracking, API/MCP uptime.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Fixter is a remote monitoring service for small teams that lets an assistant work with logs, traces, metrics, live issues and API/MCP uptime.

What you can do
Work with logs, traces and metrics collected by the Fixter monitoring service for small teams. Review live issue tracking and API/MCP uptime information. The manifest lists no individual tools, so the exact operations available to an assistant are not documented here.
When to use it
Useful when a small team already relies on Fixter for monitoring and wants an assistant to look at logs, traces, metrics, issues or uptime while troubleshooting or reporting.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package is needed. Authentication is required: OAuth 2.0 browser-based authorization is recommended, or an API key sent in the Authorization header for agents and server-to-server use.
Before you install
The connection requires credentials: either OAuth authorization or an API key in the Authorization header. Monitoring data may include sensitive operational details, so consider what the assistant is allowed to read and share.

Installation

In SourceWeft

  1. Open Fixter in the dashboard and add it to a workspace.
  2. Connect the required 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/dev.fixter%2Ffixter/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fixter": {
      "type": "http",
      "url": "https://mcp.fixter.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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
  • 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.