MCP
Use the project’s Streamable HTTP MCP endpoint:
https://PROJECT_ID.api.flexkit.io/mcpReplace PROJECT_ID with the Dashboard project ID. Configure it as a remote MCP server in a client that supports the server’s OAuth discovery flow.
Connect and verify
- Add the endpoint in your client’s remote MCP configuration.
- Follow the OAuth sign-in and consent flow with the intended Flexkit account.
- Confirm the selected project and granted connection.
- Start with schema inspection or a bounded read-only query.
- Verify the returned data against Studio before permitting mutations through the client.
Client settings differ; use your installed client’s remote-server and OAuth instructions. Do not paste a Dashboard session cookie into its configuration.
Capabilities and authority
The server provides schema search, GraphQL validation, query and mutation execution, skill listing/loading, and user-memory loading/updating. Requests act with the OAuth user’s role and space memberships. Memory is shared with that user’s Chat context.
MCP does not expose the entire Studio workflow runtime: sandbox, artifact, bulk workflow actions, and chat delivery are not part of this tool set. A client has its own execution and confirmation experience; do not assume the Studio Approvals UI mediates every client action.
Revoke an unwanted connection through the supported account authorization controls and remove it from the client. If access fails, inspect the account, project membership, consent, and project restrictions.