Citlyze

com.citlyzePublished by citlyze.comOfficial publisherv1.0.0Updated Oct 26, 2026

Read-only access to your Citlyze workspace: AI search visibility, citations, and recommendations.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server giving an assistant read-only access to a Citlyze workspace's AI search visibility, citations and recommendations.

What you can do
  • Read AI search visibility data from a Citlyze workspace.
  • Review citations collected for the workspace.
  • Retrieve recommendations surfaced by Citlyze.
  • All access is read-only; no tools are listed in the manifest, so exact operations are not documented.
When to use it
Useful when you want an assistant to answer questions about how a brand or site appears in AI search results, which citations it receives, and what Citlyze recommends, without leaving the chat.
Requirements
A remote streamable HTTP endpoint at app.citlyze.com, reachable over the network. A Citlyze account and API key, sent as a bearer token in the Authorization header; keys are created in the workspace settings.
Before you install
The API key is a secret sent in the Authorization header and grants access to your workspace data; keep it out of shared logs and revoke it if exposed. Access is described as read-only, but workspace visibility and citation data is shared with the assistant and its model provider.

Installation

In SourceWeft

  1. Open Citlyze 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/com.citlyze%2Fcitlyze/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": {
    "citlyze": {
      "type": "http",
      "url": "https://app.citlyze.com/api/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

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.