Use cases

Connect your own system over MCP

For anything without its own connector: any MCP server you expose connects with the same permission controls.

Engineering

«Can Gescon read our internal system's data?»

If you expose an MCP server, Gescon queries it with only the permissions you define on that server.

Product

«What tools does this MCP server expose?»

Gescon lists the available tools and what each one is for.

Management

«What custom connectors do we have active right now?»

A list of the connected MCP servers and since when.

Engineering

«How do I debug a response coming from our MCP?»

Every answer indicates which MCP server tool was invoked and with what parameters.

What it brings

What it reads and what it doesn't touch

The connector can only do what the MCP server itself allows. Gescon doesn't widen those permissions.

Tools exposed by the server

Not one more: Gescon only sees what the server decides to publish.

Parameters for each call

Every invocation is logged with what it was asked for.

Server response

Shown exactly as your system returns it, without reinterpreting it.

Citations to the tool invoked

Every answer indicates which MCP tool generated it.

No added permissions

If the server doesn't allow writing, neither can Gescon.

Setup

Stand up the MCP serverOn the system you want to connect, with the tools you define.

Authorise the connectionWith the credentials or token your server requires.

Validate with three questionsCheck which tool Gescon invokes before opening it to the team.

Requirements

Estimated connection time: varies by server

Same family