Caspian

io.getcaspianPublished by getcaspian.ioOfficial publisherv1.0.0Updated Nov 7, 2026

See and manage your company's apps, access, devices and spend from your AI assistant.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Caspian is a remote MCP server that lets an AI assistant view and manage a company's apps, access, devices and spend.

What you can do
  • View the company's apps, access, devices and spend
  • Manage those records from the assistant
  • No tool list is published, so exact actions are not documented
When to use it
Worth considering when you want to check or administer company apps, user access, devices or spending from within an AI assistant instead of a separate admin console.
Requirements
A remote MCP endpoint at app.getcaspian.io over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
The server is described as managing apps, access, devices and spend, so it may change or remove access and affect spending; grant it only to accounts whose permissions you accept. No tool list is published, so review the actual tools before connecting.

Installation

In SourceWeft

  1. Open Caspian 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/io.getcaspian%2Fcaspian/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": {
    "caspian": {
      "type": "http",
      "url": "https://app.getcaspian.io/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 7, 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.