Skip to main content

Local outbound bridge agent for MCP capability forwarding

Project description

mcpassistant-gateway

Async local bridge that connects outbound to the remote MCP bridge over WSS and forwards invoke requests to local MCP servers using the MCP Python client library.

Run

pip install -e .
mcpassistant-gateway

mcpassistant-gateway initializes MCP client sessions for configured mcpServers (stdio) and opens the outbound bridge connection to the remote server.

Startup token behavior:

  • If AGENT_JWT is already configured (env or config.json), startup continues without prompting.
  • If AGENT_JWT is missing, the CLI shows a styled prompt and asks you to paste the token.
  • If WebSocket auth fails with HTTP 403, the CLI asks for a fresh AGENT_JWT and retries immediately.
  • AGENT_ID is auto-derived from JWT claims (or token fingerprint fallback), so no manual AGENT_ID prompt.
  • Prompted values are saved into resolved config.json, so next runs do not ask again.

Set START_MCP_SERVERS=false if you only want the bridge process.

Configuration can be provided through .env and/or config.json.

If config.json does not exist, it is created automatically on first run with:

  • remote_server_base_url defaulting to https://hub.linkos.in/agent
  • a default mcpServers.filesystem entry scoped to your current working directory

Minimal dynamic .env:

REMOTE_SERVER_BASE_URL=https://your-remote-domain
AGENT_JWT=your_agent_jwt

With this mode:

  • REMOTE_WEBSOCKET_URL is derived as wss://.../connect
  • AGENT_ID and CAPABILITIES are derived from JWT claims (sub, capabilities) if not explicitly set
  • Local MCP calls are handled via MCP client sessions for mcpServers

mcpServers + mcpassistant-gateway-bridge

You can run MCP servers from config (supergateway-style) and derive local HTTP endpoints:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "supergateway", "--stdio", "npx", "-y", "@modelcontextprotocol/server-filesystem", "--port", "3004"],
      "port": 3004
    }
  }
}

Run one server:

mcpassistant-gateway-bridge --config ./config.json --name filesystem

Run all servers in config:

mcpassistant-gateway-bridge --config ./config.json

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mcpassistant_gateway-0.1.1.tar.gz (53.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

mcpassistant_gateway-0.1.1-py3-none-any.whl (14.6 kB view details)

Uploaded Python 3

File details

Details for the file mcpassistant_gateway-0.1.1.tar.gz.

File metadata

  • Download URL: mcpassistant_gateway-0.1.1.tar.gz
  • Upload date:
  • Size: 53.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.1

File hashes

Hashes for mcpassistant_gateway-0.1.1.tar.gz
Algorithm Hash digest
SHA256 95e465968af3c9c775a790965aa0074e4aed2edcaf77a6fd6801645ee9e6fff8
MD5 f5fb8f92ded38937ed2ceeb9640808ea
BLAKE2b-256 cd126632e77ff85ad5189dc28f4ddbf7a736923c867544fda94adfe419070a4a

See more details on using hashes here.

File details

Details for the file mcpassistant_gateway-0.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for mcpassistant_gateway-0.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 bf6fe3e68798fd4e951b5945052334979c2dded068aa791ec3ae2e5ed4be4a0b
MD5 7caa6c1985d4f9181fd216768a5cff8d
BLAKE2b-256 b2d12946db73037e60b15e8e855900e98cfa412d2a42badf82704b354708490f

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page