Connect Knowify to Claude Code

Make Claude set up and maintain jobs in Knowify. From the terminal, inside the sessions where you already work.

How do you connect Knowify to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Knowify, you add a Knowify MCP server: a small hosted service that exposes Knowify's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Knowify account. No API keys pasted into config files.

claude mcp add --transport http knowify https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Knowify once connected?

Full read-write lets Claude handle job setup and upkeep. It can create a contract job with its phases from a signed proposal, add tasks, set up clients and vendors, enter vendor bills for your review, and keep watch on new invoices and payments so billing movement reaches you without digging.

Create a contract job with phases from a signed proposal, held for your review
Add tasks to a job phase after you approve
Create or update client and vendor records after you approve
Search jobs, clients, and products by name or ID
Enter vendor bills against a job for your review
Flag new invoices and payments as they land, summarized for you

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Knowify access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Knowify API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Knowify changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Knowify connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Knowify connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Knowify account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Knowify's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Knowify?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Knowify account it signs in with. Revoking access is one click in Knowify.

More on the Knowify connector

Knowify connector for claude.ai Buildertrend + Claude Code Procore + Claude Code QuickBooks Online + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us