Project 8 — MCP server plus AI agent
Words made simple
A few useful meanings before you read the explanation.
- AI
- Software techniques for tasks such as recognizing patterns, understanding language or generating content.
- Agent
- An application that uses a model to choose its next action within defined limits. It can use tools and continue through several steps.
- MCP
- A shared protocol for connecting AI applications to tools and resources. It does not replace permission checks or application security.
More words from this lesson
- API
- A way for one piece of software to ask another for data or an action. A claims API might return the current status of a claim.
- Token
- A small piece of text processed by a model. It may be a whole word, part of a word, or punctuation.
- Schema
- A description of the fields and value types that data should contain. It helps check that an answer has the expected shape.
- Idempotency
- Making a repeated request have the same intended business effect as one request. It helps avoid duplicate submissions or payments.
- Authorization
- Checking what that identity is allowed to read or do. Being logged in does not grant access to every record.
Requirements
Expose reviewed customer lookup, order/policy lookup, ticket creation, and knowledge search to an approved host.
Architecture
Agent host → MCP client → authenticated server → authorized business tools. Existing APIs stay behind the facade.
Technologies
Compatible MCP SDK/transport, Zod/Pydantic schemas, token verification, existing service adapters.
Database design
Capability/tool version metadata, audit records, idempotent tickets, and resource ownership; business data remains canonical.
API design
MCP discovery/invocation/resource contracts plus health/admin operations; negotiate the adopted protocol version.
AI design
Host maps permitted tool definitions into model calls, applies approval policy, validates results, and bounds tool use.
Security
Trusted servers, reviewed definitions, token audience/scope checks, object authorization, safe downstream identity, and output limits.
Evaluation
Discovery scope, unknown tool, malformed args, denied objects, poisoned descriptions, duplicate tickets, and protocol errors.
Observability
Host/client/server correlation, tool versions, auth denials, latency, and redacted audit events.
Deployment
Secure remote endpoint or local process as appropriate; rotate credentials and test compatible client/server versions.
Interview questions
- “Why MCP versus REST?” Answer: standardized AI-host discovery/integration; REST can remain underneath.
- “Does OAuth grant record access?” Answer: object authorization remains separate.
Acceptance: An approved second host can reuse the same safe contracts without changing business rules.
Can you explain it without the notes?
Project 8 — MCP server plus AI agent
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
Requirements: Expose reviewed customer lookup, order/policy lookup, ticket creation, and knowledge search to an approved host.
Turn this concept into a clear answer.
Practice this conceptKeep connecting the ideas.
Next lesson: Project 9 — Deterministic plus agentic workflowAdapted from 13_AI.MD · “Project 8 — MCP server plus AI agent”. Examples are study fragments; framework behavior can depend on your version.