Discuss access.
Describe the client, workspace and business task. Eyeleven can confirm the supported access path and scope for that integration.
Build & connect / MCP
A defined connection.
Authorized access.
Connect a supported client to Eyeleven through the Model Context Protocol. Start with a workspace, a business task and the access that task requires.
The official endpoint
One address.
A defined scope.
Connect a client only after your access has been provisioned. Keep credentials in the client's secure configuration. This public page does not request or store them.
Model Context ProtocolPOST · Authorization required
https://mcp.eyeleven.com/mcpConnection path
From access to a verified client.
Three steps to an authorized workspace connection.
Set up your client.
If access is provided, use the official endpoint and authorization for your integration. Keep credentials out of public pages and shared documents.
Test authorized access.
Confirm the configured client can make an authorized request for its permitted scope. A public health response alone does not confirm this.
Integration brief
Bring one task. Define the connection.
Use these details to request access or troubleshoot a connection. Do not include credentials.
Where will you connect?
Name the MCP client, its version and the workspace you want to connect.
What should it do?
Describe one business task, the information it needs and whether it should read data or request a change.
What proves it worked?
Specify the expected result and who approves changes. For an existing connection, include the non-secret error and time it occurred.
After access is provisioned, test the permitted operation in an authorized test workspace. A public health response confirms service availability, not workspace access.
Public service information
Check gateway health.
These public endpoints report service information. They do not sign you in or prove a workspace connection.
Connect with purpose