Skip to content

MCP vs API: run one interview from a chat or from code

In short

An API gives your code a fixed set of calls, and MCP lets an AI app find a server's tools and use them while a person chats. Tracy AI Interviewer offers both, so you can ask Claude to draft and invite through its MCP server or have your own system request an interview through its API, and Tracy runs the interview either way. Your team decides which route fits the task.

What an API and MCP each do well

MCP vs API is a choice between two ways to reach the same tool. An API is a set of requests one program can make to another, and it does that job well: developers read its documentation, write the call once, and it runs the same way on every trigger with nobody watching. MCP is a standard for how an AI app finds and uses a server's tools while you chat, and it does that job well: you paste a URL, sign in, and the app asks the server what it offers. What an MCP server is has the longer definition. The two also work together: a tool on an MCP server can call an API underneath, and the MCP documentation lists API calls among the things tools do.

Neither route can sit across from the customer who cancelled. Your code can create an interview the moment the cancellation arrives, and a person in Claude can do the same by asking, but the conversation with that customer has to be held by something. That part is Tracy's.

What is the difference between MCP and an API?

An API is written for a developer, who learns the calls and builds them into code. MCP is written for an AI app, which asks the server what tools it has and then picks one to fit your request. Six differences follow from that.

Six differences between an API and an MCP server.

QuestionAPIMCP
Who uses itA developer's codeAn AI app, for a person
How it is foundRead the docs, write the callThe app asks the server what it offers
Who decidesYour code, call by callThe AI picks a tool; you approve
SetupCode and an API keyPaste a URL and sign in
When it failsA status code and a stable error code in JSONThe chat shows the problem, or the connector is off
Best forWork that runs on a triggerWork done in a chat

The discovery step is part of the protocol: a client lists a server's tools and their inputs before it uses any of them. The approval step belongs to the AI app. Claude asks before it uses a tool, and ChatGPT asks for confirmation before write actions by default.

Two squares in the grid below are mixed cases. A form you build starts with a person but calls the API through code you wrote. An agent starts from code or a schedule and finds its tools through MCP, so nobody is in the chat; with Tracy, creating, inviting and turning on a public link still wait for a person to approve a preview. In Claude, a server you add is called a connector, and connectors vs MCP covers the naming.

One task, both ways: invite five people to an interview

Take one job: set up a customer interview and invite five people. The job is the same on both routes, and each route spends its effort in a different place.

Through MCP, in Claude. With Tracy's server added, you write: "Set up a customer discovery interview for people who cancelled last month." Claude uses Tracy's tools to suggest an interview and shows you a preview. You change what you want, approve it, then ask Claude to invite five email addresses you supply, and approve the invitations. Later you ask who has finished and read the results. There is no code and no key to handle.

Through the API. A developer builds the same job into your own system, with an API key made under Integrations in your Tracy account. The key goes in the Authorization header of each call and reaches your account's interviews only. Tracy's public API guide describes three calls from a key to an invited person:

  1. List your interviews.
  2. Create one by sending who you are interviewing and what you want to find out. Tracy drafts the title, questions and result fields, and the answer carries the new interview's id. The guide's own example sends a body with two fields, participants ("Candidates for a Customer Support Lead role") and goal ("Whether they have led a small team and stay calm with upset customers").
  3. Invite a participant to it. Tracy emails them their personal link, and the answer holds the link too.

So when a customer cancels, your system can run those calls and the person gets the link with nobody typing in a chat. The guide adds two details a developer will want: a repeated call carrying the same idempotency key is not run twice, and the API allows 20 calls per account in any 10 minutes to generate questions or to create an interview without a setup, counted however the call is made, including from an AI app. Other calls are not limited.

Count the calls for five people: one to create the interview and five to invite, six in all. Only the create call counts toward the limit of 20 in any 10 minutes, so the sensible pattern is one interview and many invitations, not a new interview for each person. The Connect page links the API guide next to the MCP setup.

Four steps: a chat or API call, Tracy drafts the interview, Tracy interviews, you read what each person said.
Both routes end in the same place: a chat or an API call starts the task, Tracy drafts and runs the interview, and you read what was said. Illustration with sample content. Source: Tracy AI Interviewer Connect page.

One request starts the interview, and Tracy runs it whichever route sent it.

Two by two grid of who starts the task against how tools are found. MCP in a chat is highlighted; the API is the code square.
Who starts the task and how the tools are found: Tracy's MCP server in Claude is the person-asks, app-finds-tools square, the API is the code-starts square. Illustration with sample content. Source: Tracy AI Interviewer Connect page.

Who starts the task decides between a chat and code, and the highlighted square is the MCP route.

What Tracy adds to either route

01. Reach every person

Tracy runs the interview on video, and each person you invite starts on click, at any hour, with no scheduling and no recruiter on the call. The person being interviewed meets the same interview whichever route sent the invitation.

02. Ask the next question

Tracy follows the answer in the person's own field and waits for it. A vague reply gets a sharper question before the interview moves on.

03. Keep the evidence

Every result holds a recording, a timestamped transcript and a written assessment per question with its reasoning. Reading results returns what each person said to each question, the result fields and a note for an applicant tracking system.

Sample interview: a customer says the product was not working, and Tracy asks what it needed to do.
Tracy asks what the customer needed after hearing that it was not working, and the transcript keeps the exchange. Illustration with sample content.

A vague answer to a customer question gets a sharper one, whichever route sent the invitation.

MCP vs API: when each route fits

Reach for MCP when:

  • a person drives the work and the task changes each time;
  • you want to read a preview and approve each write;
  • you are setting something up once and do not want to write code.

Reach for the API when:

  • a system should act on a trigger with nobody in the loop, such as a new applicant or a cancellation;
  • the call is the same every time and you want exact control over it;
  • many identical requests run without a person reading each one.

If you do both, set the interview up in a chat, then let the API invite people automatically. What an MCP server is covers the MCP side in more detail, and Tracy in Claude shows the chat route end to end.

One practical difference shows up when something breaks. In the API guide every failed call returns JSON with a stable error code that your code can test for, such as unauthorized for a missing or revoked key and rate_limited once an account passes 20 question-drafting calls in 10 minutes. In the chat route there is no code to test. You look at the connector instead: whether it is switched on for the conversation, and whether Claude is waiting for you to approve a call.

Common questions

What is the difference between MCP and an API?
An API is a set of calls a developer's code makes. MCP is a standard that lets an AI app discover a server's tools and use them while you chat. A tool on an MCP server can call an API underneath.
MCP vs API for agents: which one should an agent use?
An agent working with a person in a chat benefits from MCP, because it can list a server's tools and ask for approval. An agent running without a person on a fixed trigger may call an API directly.
Does MCP replace APIs?
No. MCP sits at a different layer. A tool on an MCP server can call an API, and code can still call an API directly.
Is an MCP server an API?
Not in the sense a developer means. It is a program that follows the Model Context Protocol so AI apps can discover and call its tools.
Does Tracy offer MCP, an API or both?
Both. The MCP server is at tracyinterview.ai/mcp, for use from Claude, ChatGPT and other MCP apps. The API is for a customer's own system to request an interview and hand the person the link.

Draft one interview in Claude

Connect Tracy to Claude and draft one interview by asking in a chat. You approve the preview, and the first 3 results are free.

Try it free (opens in a new tab) Book a demo (opens in a new tab)

Your first 3 results are free. No card needed.

Sources