Whatever message this page gives is out now! Go check it out!
Custom URI Schemes
Last update:
May 18, 2026
Resources are identified by URIs, and MCP does not limit you to file:// or http://. Your server can define custom URI schemes to model your domain in a user-friendly way.
Overview
Resources are identified by URIs, and MCP does not limit you to
file:// or http://. Your server can define custom URI schemes to model your domain in a user-friendly way. Examples:
log://today– today’s aggregated log viewreport://sales/2025-02-01– sales report for a given datecustomer://12345/profile– a customer profile snapshotquery://orders/open– current open orders dataset
These schemes are:
- Logical names, not real network protocols.
- Resolved by read handlers on your MCP server.
- A way to give the model (and users) stable, memorable identifiers for important data.
How Custom Schemes Help You
Compared to raw paths like
file:///var/app/data/sales-week-2025-02-01.json, custom schemes: - Hide low-level storage details (where and how data is stored).
- Express intent and semantics (this is a “report”, not just a file).
- Make it easier to ask for resources by name:
- “Read report://sales/last-week and summarize anomalies”
For you as a user:
- You work with resource names and URIs that reflect business concepts.
- The same URI can be backed by files, databases, or APIs without changing your prompts.
- You don’t need to remember file system layouts or database schemas.
URI Structure
A custom URI generally has:
- A scheme:
logs,reports,customer, etc. - A path or identifier:
/today,/weekly/2025-02-01,/12345/profile
For example:
logs://app/todayreports://finance/quarterly/2025-Q1customer://12345/tickets/open
The scheme and path are interpreted by your server’s read handler (see next section).
We're glad. Tell us how this page helped.
We're sorry. Can you tell us what didn't work for you?
Share additional feedback to help us improve.
0/255
|
