# Toolstile [Verified owner] [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://toolstile.com/  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 1  
**Directory Page:** https://allmcps.com/mcp/toolstile

## Description
Managed MCP gateway with per-agent permissions, shared accounts, and activity logs. Connect remote servers through one endpoint: https://mcp.toolstile.com/mcp (Streamable HTTP and OAuth).

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "toolstile": {
    "url": "https://mcp.toolstile.com/mcp"
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/toolstile/readme_