COUNTCOUNT
Sign Up

AI

Build with COUNT's AI toolkit

Most partners start with the Prompt Generator to ship a Partner API integration with an AI coding assistant. Use MCP or the CLI when you want workspace automation inside an agent.

Integration-first workflow
Recommended

Prompt Generator

Most partners start here to scaffold OAuth, HMAC, and REST code in Cursor or Claude Code. Compose detailed prompts for bank feeds and REST endpoints against the Partner API.

  • OAuth & token refresh
  • Signed HTTP examples
  • Bank connection flows
Open Prompt Generator
Local agent setup

COUNT CLI

OAuth login on your machine and a stdio MCP server for Claude Code, Cursor, and other agent runtimes.

  • Local credentials
  • MCP config export
  • Workspace login
Set up the CLI
Workspace automation

MCP Server

0 typed tools for workspace data, over stdio locally or OAuth remotely for Claude.ai and ChatGPT connectors.

  • COUNT_* tool catalog
  • Remote OAuth
  • Same API paths
Explore MCP tools
Ready-made copy

Prompt Library

Browse copy-paste prompts by category and difficulty. Integration prompts include REST snippets; MCP prompts target COUNT_* tools.

  • 17 categories
  • Difficulty tags
  • Code snippets
Browse prompts

Which surface should I use?

Match the tool to your build target. You can use more than one — many teams generate integration prompts first, then wire MCP for internal ops automation.

Your product on the Partner API

OAuth, HMAC, REST. Build COUNT into your own app or backend.

Prompt Generator

A coding agent on your laptop

Claude Code, Cursor, or Windsurf with local login and stdio MCP.

COUNT CLI

A hosted AI connector

Claude.ai or ChatGPT calling COUNT over remote OAuth MCP.

Remote MCP

Remote MCP endpoint

https://api.getcount.com/mcpSetup guide

Quick start

For local MCP in a coding agent, install the CLI, sign in, and print MCP configuration:

Terminal
npm install -g @countfinancial/cli
count login
count mcp print-config

Two paths, one API

Build an integration with the Prompt Generator (REST + OAuth + HMAC). Automate a workspace with CLI or remote MCP (COUNT_* tools). Local and remote MCP expose the same tool names and partner API paths.