Integration · Local MCP server

Connect local MCP servers through Outpost

Connect an MCP server from an internal network to selected assistants without exposing it publicly.

A local MCP server can be made available to selected assistants through the meinGPT Outpost. The server remains on the internal network and describes its own tools; the Outpost carries approved calls through its outbound connection.

An administrator registers the address and credentials on the Outpost, then shares the service in meinGPT. Only then can an assistant discover and invoke the server's tools. People reach the service only through assistants shared with them.

Technical frame
Local MCP server
meinGPT
Source
Local MCP server
Capability
Use internal MCP tools in approved assistants
Connection
Administrator registration on the Outpost, sharing in meinGPT and server-side authentication
Data residency
The server and connection secrets remain on the local network; calls travel through the outbound Outpost connection

Source, permissions, and data residency are documented separately for each connector.

Setup in the docs

Typical workflows

  • Use internal tools
  • Query existing systems
  • Run internal actions

What the integration makes possible

01

Use internal tools

Attach domain-specific MCP tools from the local network to an assistant.

02

Query existing systems

Invoke read tools from an internal MCP server in a controlled way.

03

Run internal actions

Expose server actions only through deliberately approved assistants.

Review the prompt and result openly

Prompt

Use the internal MCP tool to retrieve order 4711 and summarize its open steps.

Result

Order 4711 is in production. Quality inspection and shipping approval remain open.

Does this connection fit your use case?

We clarify the source, permissions, and connection required for the concrete use case. If the existing integration fits, you can move straight to setup afterwards.

Security and operations

Registration, sharing and audit provide the access boundary. Credentials remain on the Outpost; the local server should also enforce authentication and narrowly scoped tools.

Known limitations

  1. 01Private Beta. The connected MCP server determines the available functions and whether they can write data.

Frequently asked questions

No. The Outpost establishes the connection from the local network to meinGPT.