# Calaf [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/gallaghern51-art/calaf-mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/calaf-2

## Description
Connect your Calaf recruiting book: validate and import seeds; people arrive staged for your review.

## Tools
Capabilities this server exposes over MCP:

- **Organizations** — deduped account-wide by name, then joined to the workspace
- **Templates** — deduped within the workspace

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "calaf": {
    "url": "https://calaf.ai/api/mcp"
  }
}
```

## Documentation

## What the Calaf MCP server does

The Calaf MCP server links an AI assistant with a Calaf recruiting account. It supports structured seed workflows, recruiting workspaces, organization and contact records, firm research, work logs, applications, and follow-up tasks. The account endpoint uses OAuth 2.1 with dynamic client registration, while the separate seed-tools endpoint does not require authentication.

A seed can contain organizations, contacts, templates, preparation questions, key dates, vocabulary, and planner data. Before import, the assistant can retrieve Calaf’s seed specification and run the document through the same parser used by the application. Validation returns section counts and issues with paths, messages, and severity levels.

## How it works

Connect an MCP client to `https://calaf.ai/api/mcp-account` using Streamable HTTP. After authorization, the assistant can list available workspaces and use a workspace key when importing a seed. Imports are idempotent and non-destructive: organizations are deduplicated across the account before being associated with the workspace, templates are deduplicated within the workspace, and preparation questions are deduplicated account-wide.

Contacts follow a review step rather than being written directly. People included in an import are staged as a batch that the user can accept, edit, discard, or undo. A person must be associated with an organization to be stageable. The assistant can also export a workspace back into a seed, with people, personal notes, and previously seeded content excluded unless requested.

The server includes firm-profile operations that expose module schemas, read current data with field provenance, and submit sourced research to the user’s overlay. User-entered values are protected from assistant overwrites, and unsupported claims are dropped when sources are missing.

## Setup and configuration

For Claude’s web or desktop interface, add a custom connector named `Calaf` with the account endpoint and complete the Calaf consent flow. Claude Code can add the remote server with:

```bash
claude mcp add --transport http calaf https://calaf.ai/api/mcp-account
```

Other MCP clients should add the same remote Streamable HTTP endpoint and support dynamic client registration, PKCE, and protected-resource metadata discovery. Custom connectors require a paid claude.ai plan at the Pro tier or above.

Without an MCP client, use Calaf’s guide and settings prompt to teach an assistant the seed format, validate through the open validator API, and import the resulting file from Calaf workspace settings.

## Tools and capabilities

The Calaf MCP server provides tools for:

- Reading and validating the seed format, importing selected seed sections, and exporting workspace data.
- Listing workspaces, contacts, firms, and recruiting applications.
- Reading, submitting, and managing sourced firm profiles and firm work logs.
- Logging touchpoints, updating existing contacts, and adding dated tasks.
- Staging imported people for review rather than creating them silently.

Touchpoint logging can update contact status, schedule follow-ups, create a next-day thank-you task, and move a researching firm to networking when appropriate. Contact updates preserve existing user values, while assistant-authored firm-work entries can be removed by the assistant; manually entered items cannot.

## Limitations and notes

The account tools require Calaf authorization. People cannot be created directly through the contact update operation; they must arrive through a seed import and reviewable staging. Firm-profile submissions require sources, and claims without them are discarded. Imports do not delete or overwrite existing records, and identity fields only fill empty values during contact updates. Privacy controls on export determine whether people, notes, and seeded content are included.

_Full upstream README: https://allmcps.com/mcp/calaf-2/readme_