MCP integration

KeenKind connects to local and remote servers implementing Model Context Protocol. Before adding one, verify that it runs in its official client or test tool.

Choose a connection method

Method	Suitable for	Required information
stdio	Local programs and servers under development	Command, arguments, environment variables
HTTP	Deployed shared services	URL and authentication

stdio example

In Settings > Extensions > MCP > Add manually, enter:

Name: My MCP
Method: stdio
Command: my-mcp-server
Arguments: --workspace C:/projects/demo

The command must run on the current system. Use environment-variable fields for keys rather than arguments, names, or descriptions.

HTTP example

Name: Team MCP
Method: HTTP
URL: https://mcp.example.com

Use HTTPS and a least-privilege account. Shared-service administrators manage their own access control, rate limits, and auditing.

Tool design

For reliable model use:

• Keep names short and meaningful.
• Describe when to use the tool and its result rather than internal implementation.
• Keep input schemas small and field names stable.
• Clearly document required fields, enums, and formats.
• Return structured results and readable errors.
• State the impact scope of modifying operations.

Avoid combining unrelated operations or requiring hard-to-verify command strings.

Verification

1. Add and enable the server.
2. Confirm its details page lists tools.
3. Call a read-only tool in Ask for approval mode.
4. Check that successful and failed results are understandable.
5. Test cancellation, restart, and missing credentials.
6. Then test writes or external actions.

For connection failures, first verify the server in a terminal, then check commands, URLs, environment variables, and platform support in KeenKind.