Toolport

What tsouth89/toolport does

tsouth89/toolport MCP server acts as a local management layer for MCP servers. Instead of configuring the same server separately in each AI application, you add or import the server once, authenticate it, and connect supported clients through Toolport. The project describes support for Claude, Cursor, Codex, VS Code, and other AI clients; the available client setup depends on the documented integrations.

The gateway is intended for local use. The desktop application is available for Windows, macOS, and Linux, and the project also documents headless gateway and Docker scenarios. The desktop app and gateway are MIT licensed.

How it works

Toolport maintains a shared collection of MCP server configurations. You can add a server from its catalog, import an existing setup, or paste a server configuration. After authentication, the server can be made available to connected AI clients through the Clients area.

Profiles control which servers each client can access. Tool discovery is lazy: an agent searches for available tools when needed instead of receiving every tool definition at startup. This is designed to limit the amount of MCP metadata placed in an agent's context.

Credentials are kept in the operating system keychain rather than client configuration files. Toolport also provides controls for disabling tools, requiring approval for destructive calls, and reviewing activity. Agent rules can be written centrally and previewed before they are applied to supported clients.

Setup and configuration

To use tsouth89/toolport MCP server, download Toolport for Windows, macOS, or Linux, or obtain an installer from GitHub Releases. Add an MCP server through the catalog, import an existing configuration, or paste its configuration manually. Authenticate that server in Toolport, then open the Clients section and connect the AI applications you want to use.

The repository links to separate documentation for supported clients, profiles, environment variables, configuration, agent rules, permissions, troubleshooting, and headless operation. These documents should be consulted for client-specific setup details rather than assuming every client uses the same configuration format.

The project also describes Toolport Teams, with hosted and self-hosted options for sharing server configuration and policies while individual users retain their own credentials.

Tools and capabilities

The material supports these management capabilities:

• Register MCP servers from a catalog or existing configuration.
• Authenticate servers once for reuse across connected clients.
• Select accessible servers through profiles.
• Discover tools on demand instead of loading all definitions initially.
• Keep server credentials in the OS keychain.
• Disable selected tools and request approval for destructive calls.
• Review tool activity in one place.
• Share agent rules across supported clients with a preview before changes.

Limitations and notes

tsouth89/toolport MCP server is a gateway and manager, not a catalog of domain-specific tools by itself. Its usefulness depends on the MCP servers you connect and the clients supported by its configuration workflow. The excerpt does not provide a complete client compatibility matrix, command-line installation command, or required environment-variable list. It also distinguishes the local desktop application from documented headless and team deployment options, so deployment behavior may vary by setup.

Getting started with this tsouth89/toolport MCP server

Always refer to the official documentation for the most accurate and up-to-date information.