Skip to content
ToolCargo

The MCP directory / Open to explore

MCP server directory.
Find your next tool.

Search 3,974 indexed servers from the official MCP Registry and selected vendor documentation. Find remote endpoints and local packages, inspect the publisher’s setup details, then connect in your AI client.

Where will your next task take you?

Code & developmentResearch & knowledgeData & databases

Free discovery · no account · no API key

Let your agent do the finding.

Paste into your AI agent
Read https://toolcargo.com/agents.txt, then find the MCP servers I need and help me connect them. Ask me what I want to do first.

Or add https://toolcargo.com/mcp as a Streamable HTTP MCP server. Discovery is free and needs no account.

Compare task fit, publisher, permissions and a small acceptance test with the MCP server selection guide.

Connect directly to official MCP servers

Vendor setup guides for your existing accounts. These connections run with the vendor; ToolCargo does not host them or supply their credentials.

AirtableReview a project tracker without changing its records.Setup guide →HubSpotReview deal status in an existing CRM pipeline.Setup guide →FigmaUse a selected design as context for a component implementation.Setup guide →LinearTriage existing issues without changing their status.Setup guide →

Browse the remote MCP server directory →

Not sure which connection to choose? Read local vs remote MCP servers. Building a discovery workflow? See the MCP server search API reference.

Amazon Web Services MCP

Close details

Get a non-expert from zero to a Slack-delivered, plain-English, waste-flagged AWS bill breakdown

Directory identity: io.github.Servosity/aws-billing-mcp · Version: 0.1.4

Publisher connection metadata
{
  "remotes": [],
  "packages": [
    {
      "registryType": "mcpb",
      "identifier": "https://github.com/Servosity/msp-skills/releases/download/aws-billing-v0.1.4/aws-billing-mcp.mcpb",
      "version": "0.1.4",
      "fileSha256": "a2ef864f2de132358c2cc9ae3afb6e09b59baa0f06c24944c82ac9f8dc7a85b0",
      "transport": {
        "type": "stdio"
      },
      "environmentVariables": [
        {
          "description": "Access key ID for an IAM principal with Cost Explorer read access. Resolved by the AWS SDK's default credential chain.",
          "isRequired": true,
          "isSecret": true,
          "name": "AWS_ACCESS_KEY_ID"
        },
        {
          "description": "Base URL for the AWS Billing Intelligence API. Leave the prefilled default unless your account uses a different regional or self-hosted host.",
          "default": "https://ce.us-east-1.amazonaws.com",
          "name": "AWS_BILLING_BASE_URL"
        },
        {
          "description": "Slack channel or DM ID that `report --slack` posts to by default (the --slack-channel flag overrides it). Leave blank to pass the destination on every run.",
          "name": "AWS_BILLING_SLACK_CHANNEL"
        },
        {
          "description": "Region for the EC2, CloudWatch and S3 calls. Cost Explorer is always served from us-east-1 regardless of this value.",
          "default": "us-east-1",
          "name": "AWS_REGION"
        },
        {
          "description": "Secret access key paired with AWS_ACCESS_KEY_ID.",
          "isRequired": true,
          "isSecret": true,
          "name": "AWS_SECRET_ACCESS_KEY"
        },
        {
          "description": "Session token, required only when the keys above are temporary STS or SSO credentials. Leave blank for long-lived IAM user keys.",
          "isSecret": true,
          "name": "AWS_SESSION_TOKEN"
        }
      ]
    }
  ]
}

Remote URLs go into your client's MCP settings. Local packages need a compatible runtime. Check required headers, environment variables, permissions and provider costs before setup.

Publisher repository ↗

3,974 results

Index updated 2026-10-02

PreviousNext results

This directory combines dated registry listings and selected vendor-documentation entries. Documentation checks are not live account or client verification. Third-party servers run with their own providers, credentials and pricing. ToolCargo discovery supplies setup metadata; it does not run their tools. Explore ToolCargo's hosted connectors.