Log inSubmit server
Toolstile logo

Toolstile

Managed MCP gateway for connecting agents to remote servers with permissions, shared accounts, OAuth, and activity logs.

InstallWebsite
Get support Full README Compare alternatives Embed widget

Install Toolstile

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "toolstile": {
      "command": "claude",
      "args": [
        "mcp",
        "add",
        "--transport",
        "http",
        "toolstile",
        "https://mcp.toolstile.com/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Hosted endpointLive · 3d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 3d ago · Nov 10, 2026, 19:15 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.toolstile.com/mcp
We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

claude mcp add --transport http toolstile https://mcp.toolstile.com/mcp

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

Toolstile MCP server provides a managed gateway for connecting agents to remote MCP servers through one Streamable HTTP endpoint. Toolstile adds per-agent permissions, shared account handling, and activity logs around those connections, with OAuth supported at the gateway endpoint. Reach for it when multiple agents need centralized access controls and a shared connection path to remote MCP servers.

Use cases

  • Centralize access to multiple remote MCP servers
  • Enforce different permissions for individual agents
  • Share account access across cooperating agents
  • Review agent activity through centralized logs

Key features

  • Managed gateway for remote MCP servers
  • Per-agent permissions
  • Shared accounts
  • Activity logs
  • Streamable HTTP endpoint
  • OAuth authentication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

6/6 checks healthy over the last 23d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity1 upvotesConfig copies, upvotes, and views on AllMCPs.

How Toolstile works

What Toolstile does

Toolstile MCP server acts as a managed gateway between MCP clients and remote MCP servers. Instead of configuring each remote server as a separate connection for every agent, agents can use the Toolstile endpoint as a common access point:

https://mcp.toolstile.com/mcp

The gateway focuses on administration around remote MCP access. It supports permissions assigned per agent, shared accounts, and activity logs. These features make Toolstile suitable for setups where several agents or users need access to remote servers while maintaining a central control point.

How it works

Agents connect to Toolstile through the gateway endpoint using Streamable HTTP. The gateway then provides access to remote MCP servers connected through Toolstile. OAuth is supported for authentication at the endpoint.

The connection model separates the agent from the individual remote-server connections. Agents use the Toolstile gateway, while Toolstile manages the configured remote servers and applies the access rules associated with each agent. Shared accounts allow multiple agents to use common account access where that arrangement is appropriate. Activity logs provide a record of gateway activity for operational review.

This architecture is intended for organizations or projects that need one endpoint rather than independently managed remote-server connections across multiple agents.

Setup and configuration

Configure an MCP client to connect to the Toolstile Streamable HTTP endpoint:

text
https://mcp.toolstile.com/mcp

The endpoint uses OAuth, so the client connection must support the authentication flow required by the gateway. After connecting, access is governed through Toolstile’s per-agent permissions and shared-account configuration. Remote servers are reached through the gateway rather than by replacing the endpoint with a separate URL for each server.

Tools and capabilities

Toolstile’s documented capabilities center on gateway management rather than a fixed, built-in tool catalog:

  • Connect remote MCP servers through one endpoint.
  • Apply permissions separately for each agent.
  • Share account access across agents.
  • Authenticate connections with OAuth.
  • Record activity in logs.
  • Serve connections over Streamable HTTP.

The available MCP tools depend on the remote servers connected through the gateway. Toolstile therefore fits deployments where the set of remote capabilities may be managed centrally rather than embedded in one local server package.

Limitations and notes

Toolstile is a gateway, so its usefulness depends on the remote MCP servers attached to it and on the MCP client’s support for Streamable HTTP and OAuth. It should be evaluated as an access and routing layer for remote servers, not as a standalone replacement for those servers’ domain-specific capabilities. The shared-account model should also be matched to the access boundaries required by each agent.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Toolstile

Toolstile is an MCP server that connects agents to remote MCP servers through one managed gateway endpoint. Its main capabilities include per-agent permissions, shared accounts, activity logs, Streamable HTTP transport, and OAuth authentication. Agents use the gateway instead of configuring each remote server as a separate connection.

Connect an MCP client to https://mcp.toolstile.com/mcp using Streamable HTTP and OAuth. Toolstile is accessed through this managed remote endpoint, which routes agents to connected remote MCP servers and applies the configured permissions and account settings.

Yes, Toolstile supports OAuth at its MCP gateway endpoint. Configure the client to use https://mcp.toolstile.com/mcp and complete the OAuth flow required by the gateway.

Yes, Toolstile provides per-agent permissions. Use the gateway to apply different access rules to agents while connecting them to remote MCP servers through the shared endpoint.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewToolstile AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/toolstile?style=directory)](https://allmcps.com/mcp/toolstile)
HTML Embed
<a href="https://allmcps.com/mcp/toolstile"><img src="https://allmcps.com/api/badge/toolstile?style=directory" alt="Toolstile on AllMCPs" /></a>