Kepler CRM

io.github.briantoogeePublished by GitHub account briantoogeev1.0.1Updated Oct 24, 2026

Search recruiting CRM records, manage candidates, jobs, pipelines, notes and tasks with OAuth.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search and manage recruiting CRM records — candidates, jobs, pipelines, notes and tasks — through an OAuth-protected remote endpoint.

What you can do
Kepler CRM is a hosted recruiting CRM server reached over streamable HTTP at a remote endpoint. According to its description, it lets an assistant search CRM records and manage candidates, jobs, pipelines, notes and tasks. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering when a recruiting team already uses Kepler CRM and wants an assistant to look up or update candidates, jobs, pipelines, notes and tasks without switching tools.
Requirements
A remote MCP endpoint; no local package or runtime is needed. OAuth authentication is required, so the user needs a Kepler CRM account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server can manage CRM records, which likely includes creating, changing or deleting candidates, jobs, pipelines, notes and tasks; review what the assistant is allowed to modify. Access is granted through OAuth, so check which account and permissions you authorize. Recruiting data is sent to the remote service.

Installation

In SourceWeft

  1. Open Kepler CRM 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/io.github.briantoogee%2Fkepler-crm/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": {
    "kepler-crm": {
      "type": "http",
      "url": "https://app.keplercrm.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. v1.0.1LatestSep 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.