Infrapage

page.infraPublished by infra.pageOfficial publisherv0.8.0Updated Oct 24, 2026

Read-only access to your Infrapage dashboards: pages, widgets, live values, weekly recaps.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Gives an assistant read-only access to your Infrapage dashboards, including pages, widgets, live values and weekly recaps.

What you can do
Infrapage exposes your dashboards to an assistant in read-only form. It covers pages, widgets, live values and weekly recaps, so the assistant can look up what a dashboard shows and report current figures. No tool list is published, so the exact operations are not documented here.
When to use it
Useful when you keep dashboards in Infrapage and want an assistant to read them, for example to check current values or summarize a weekly recap without opening the dashboard yourself.
Requirements
A remote MCP endpoint at the provider's site, reached over streamable HTTP. Sign-in is by OAuth and is required; no environment variables or headers are declared.
Before you install
Access is described as read-only, but it still exposes your dashboard contents to the assistant, so review what those dashboards contain before connecting. Authorization is granted through OAuth to your Infrapage account.

Installation

In SourceWeft

  1. Open Infrapage 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/page.infra%2Fmcp/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": {
    "infrapage": {
      "type": "http",
      "url": "https://infra.page/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. v0.8.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

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

Other Infra integrations