Kovca

io.kovcaPublished by kovca.ioOfficial publisherv1.0.0Updated Nov 7, 2026

Build, test, publish, and run Kovca workflows from AI agents over remote MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an AI assistant build, test, publish and run Kovca workflows from an agent.

What you can do
  • Build Kovca workflows from an AI agent
  • Test and publish workflows
  • Run existing workflows
  • All actions go through the remote Kovca MCP endpoint at kovca.io
When to use it
Useful when you already work in Kovca and want an assistant to create, validate, publish or execute workflows without switching to the Kovca interface.
Requirements
A remote streamable HTTP endpoint at kovca.io; no local package. A Kovca workspace API key sent as a Bearer token in the Authorization header. Instant Workflow keys are not accepted for MCP.
Before you install
The Authorization header carries a Kovca workspace API key, so treat it as a secret and prefer a scoped key. Publishing and running workflows can change live automation, so review what the assistant does before enabling it.

Installation

In SourceWeft

  1. Open Kovca in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.kovca%2Fmcp/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.

{
  "mcpServers": {
    "kovca": {
      "type": "http",
      "url": "https://kovca.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 7, 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.