Give Kendr the right instructions and tools.
Skills teach Kendr how to handle a repeatable job. MCP servers give Kendr access to trusted tools and data. Install a skill pack from Kendr Desktop, connect remote MCP servers from your account, and decide exactly which capabilities can be used.
Skills and MCP are different
| Skill | MCP server | |
|---|---|---|
| Purpose | Gives Kendr workflow instructions, domain guidance, checks, and expected output. | Exposes callable tools and external data through the Model Context Protocol. |
| Example | A postmortem skill tells Kendr how to structure impact, timeline, causes, and actions. | A Grafana MCP server can query dashboards, logs, alerts, or incidents. |
| Where to add it | Install a skill pack from Skills → Marketplace in Kendr Desktop. | Add a remote endpoint under MCP servers, or install a desktop pack that bundles a local server. |
| Security boundary | Review what the skill instructs Kendr to do. | Trust the server, limit allowed tools, protect its token, and review consequential actions. |
A pack can combine workflow instructions with one or more MCP servers. The skill explains when and how to work; MCP supplies the tools.
Install a skill pack in Kendr Desktop
- 1Open Kendr DesktopSign in with the Kendr account you use for Cloud and API access.
- 2Open Skills → MarketplaceSearch by pack name, workflow, tool, or category.
- 3Review the packRead its description, included skills, MCP servers, tool count, version, source, and any credential requirements.
- 4Install and enableInstall the pack, then enable the pack or only the individual skills you want Kendr to use.
- 5Provide required connectionsIf the pack needs a service token, local runtime, or app connection, complete that setup before the first task.
- 6Run a matching taskDescribe the outcome in Chat or agentic mode. Kendr can select the enabled skill when its instructions match your request.
Kendr Desktop compares installed pack versions with the hosted catalog and can offer an update when a newer version is available.
Connect a remote MCP server
Use this flow for a trusted MCP endpoint that supports Streamable HTTP or HTTP/SSE over HTTPS.
- 1Get the official endpointCopy the public MCP URL from the server provider. Confirm the hostname and documentation before entering a token.
- 2Open MCP serversSign in and open Account → MCP servers.
- 3Describe the serverEnter a human-readable name, a unique server label, its HTTPS endpoint, and a description of when Kendr should use it.
- 4Limit tools when possibleEnter a comma-separated allowlist such as search, fetch. Leave it empty only when every tool exposed by the server is appropriate.
- 5Add authorizationIf required, paste the OAuth access token or bearer token. Kendr stores it separately and does not display the full value again.
- 6Trust and enableConfirm that you trust the server and its tools, then enable it for Chat.
- 7Activate it in ChatOpen Chat → Tools, select the server, and run a read-only request first to confirm the connection.
The Cloud connection screen requires a public HTTPS endpoint. Local stdio servers are normally supplied through Kendr Desktop skill packs and run on the computer where Desktop is installed.
A registered custom server is callable through the hosted model API with {"type": "kendr_mcp", "server_id": "mcp_..."}. This is intentionally separate from OAuth app connectors, which use {"type": "kendr_app", "selection": "auto"} for authenticated discovery and relevance selection. MCP servers must be enabled and trusted; Kendr injects stored authorization server-side. See Call remote MCP tools.
MCP connection fields
| Field | What to enter |
|---|---|
| Name | A clear label for people, such as “Company knowledge” or “Production Grafana.” |
| Server label | A stable identifier using letters, numbers, underscores, or hyphens, such as company_knowledge. |
| MCP endpoint | The complete provider URL beginning with https://. |
| Description | What the server provides, when Kendr should use it, and important boundaries. |
| Allowed tools | An optional allowlist of exact tool names. Use it to keep unused or high-risk tools unavailable. |
| Bearer token | An optional service token. Enter it only on Kendr's secure connection screen. |
| Trusted | Your confirmation that you recognize the provider and accept that its tools may receive relevant conversation context. |
| Enabled | Whether the server can currently be selected in Chat. |
Connect MCP through the API
Signed-in applications can create the same account-scoped MCP configuration with POST /api/me/mcp-servers.
curl https://kendr.org/api/me/mcp-servers \
-X POST \
-H "X-Kendr-Session: $KENDR_SESSION" \
-H "Content-Type: application/json" \
-d '{
"name": "Company knowledge",
"server_label": "company_knowledge",
"server_url": "https://mcp.example.com/mcp",
"description": "Search approved company documentation.",
"allowed_tools": ["search", "fetch"],
"authorization": "YOUR_BEARER_TOKEN",
"trusted": true,
"enabled": true
}'
List configurations with GET /api/me/mcp-servers. Update or delete one server at /api/me/mcp-servers/{server_id}. Treat the authorization value as a secret and never log the request body.
Use MCP tools safely
- Connect only servers whose publisher, hostname, permissions, and privacy policy you trust.
- Start with read-only tools and a narrow allowlist. Add write or destructive tools only when you need them.
- Assume a selected tool may receive the relevant prompt, file content, or conversation context needed to complete its call.
- Review proposed sends, changes, deployments, purchases, deletions, and other consequential actions before allowing them.
- Rotate service tokens on a schedule and immediately after suspected exposure.
- Disable or delete a server that behaves unexpectedly; removing it prevents Chat from using its tools.
All available skill and MCP packs
The catalog currently includes 33 packs. Open Skills Marketplace for live versions, tool counts, installation sources, and new additions.
Official and verified MCP connections
Engineering, cloud, and operations
Productivity, data, research, and content
Travel
Community
Troubleshooting
| Problem | Check |
|---|---|
| A skill does not activate | Confirm the pack and individual skill are installed and enabled, then describe a task that matches the skill's purpose. |
| An MCP server will not save | Use a valid https:// endpoint, a unique server label, and confirm the trust checkbox. |
| The connection saves but tools fail | Confirm the server supports Streamable HTTP or HTTP/SSE, the token is valid, and the allowed-tools names exactly match the server. |
| A tool is missing | Edit the server's allowed tools, or leave the allowlist empty only when all of its tools are acceptable. |
| A token changed | Edit the connection and enter the replacement token. Disable the connection until the new credential works. |