Command+K

com.commandpluskPublished by commandplusk.comOfficial publisherv1.1.0Updated Oct 24, 2026

Set up and run an in-product AI assistant: widgets, knowledge, MCP connections, usage.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowAI & ML

Overview

AI-generated overview

A remote MCP endpoint for setting up and running an in-product AI assistant, covering widgets, knowledge, MCP connections and usage.

What you can do
Command+K is a hosted, remote MCP server reached over streamable HTTP at the provider's endpoint. According to its registry description, it lets an assistant set up and run an in-product AI assistant, working with widgets, knowledge, MCP connections and usage. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to help configure and operate an embedded AI assistant inside a product, including its widgets, knowledge sources, MCP connections and usage tracking.
Requirements
A remote endpoint at the provider's address over streamable HTTP. OAuth authentication is required, so a Command+K account and an OAuth authorization flow are needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth, so review which permissions the authorization requests before connecting. The server can configure an in-product assistant, its knowledge and its MCP connections, which may change settings or data in your Command+K workspace. No tool-level details are published, so confirm what it can modify before use.

Installation

In SourceWeft

  1. Open Command+K in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.commandplusk%2Fcommand-k/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "command-k": {
      "type": "http",
      "url": "https://commandplusk.com/api/public/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.