Source

app.sourcePublished by source.appOfficial publisherv1.0.0Updated Nov 5, 2026

Marketing attribution and analytics for websites connected to Source.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP endpoint from Source that gives an assistant access to marketing attribution and analytics for websites connected to Source.

What you can do
  • The manifest lists no tools, so capabilities are known only from the short description.
  • It is described as providing marketing attribution and analytics for websites connected to Source.
  • An assistant connected to it would work with attribution and analytics data for those sites rather than with general web content.
When to use it
Consider it when you already use Source for marketing attribution and want an assistant to work with the attribution and analytics data of your connected websites.
Requirements
A remote MCP endpoint at api.source.app over streamable HTTP; no packages, environment variables or headers are declared. Authentication is OAuth and required, so a Source account with the relevant site connections is needed.
Before you install
OAuth access is required, so the assistant receives a token scoped to your Source account; review what that grant covers. The manifest lists no tools, so what the assistant can read or change cannot be verified from the listing. Analytics data about your websites is handled by a third-party service.

Installation

In SourceWeft

  1. Open Source 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/app.source%2Fsource/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": {
    "source": {
      "type": "http",
      "url": "https://api.source.app/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.0LatestNov 5, 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.

Other Source integrations