Corpole

com.corpolePublished by corpole.comOfficial publisherv2.0.0Updated Oct 24, 2026

Requirements authority for AI coding agents: binding requirements and acceptance criteria.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Corpole is a remote MCP server that gives AI coding agents binding requirements and acceptance criteria to work against.

What you can do
Supplies binding requirements for AI coding agents to follow during development work. Provides acceptance criteria that agent output can be checked against. Acts as a requirements authority, so an assistant can align its coding work with defined expectations rather than guessing. No individual tools are listed in the available material, so the exact operations are not documented here.
When to use it
Useful when an AI coding agent should build against explicit, binding requirements and acceptance criteria rather than inferred intent, for example to keep generated code aligned with agreed specifications.
Requirements
A remote server reached at its hosted endpoint over streamable HTTP. Authentication is required via OAuth. No packages, environment variables or headers are declared.
Before you install
Access requires an OAuth sign-in to a third-party service, so account data and requirements content are shared with that provider. The available material does not describe what the server writes or changes, so confirm before letting an agent act on it.

Installation

In SourceWeft

  1. Open Corpole 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.corpole%2Frequirements/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": {
    "corpole": {
      "type": "http",
      "url": "https://corpole.com/api/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. v2.0.0LatestSep 23, 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.