Give an AI assistant safe vFound tools
The vFound MCP server runs every tool through the documented REST API, so venue boundaries, billing access, product access and API-key scopes still apply.
MCP for AI assistants and vFound, working together
- Lets assistants find desk records and inspect expected visitors, waiting parcels and overdue equipment.
- Offers narrow write tools for inviting a visitor, logging or reminding a parcel and extending an equipment due time.
- Never exposes tools that hand an item over, sign someone in or out, decide a claim or delete a record.
Connect it in three clear steps
- 1
Create a scoped vFound key
Open Settings, For developers and create an API key with only the scopes the assistant needs.
- 2
Add the MCP server
Use https://vfound.io/api/mcp as the HTTP MCP URL and send Authorization: Bearer followed by the key. Follow your client’s MCP server instructions.
- 3
Check the visible tools
Open the client’s tool list. vFound filters it from the key’s scopes and the products open for that venue.
Details before you connect
- MCP access works in clients that can send a custom Authorization header to a remote HTTP MCP server, including Claude Code, Cursor and Visual Studio Code.
- The key remains a secret. Revoke it from vFound Settings at any time.
Frequently asked questions
Can the assistant see every vFound record?+
No. It sees one venue, the products open for that venue and only the operations allowed by the key’s scopes.
Can an assistant hand over an item or decide a claim?+
No. Those tools are deliberately not exposed over MCP.
Which clients work?+
The setup is documented for Claude Code, Cursor and Visual Studio Code, which accept a remote HTTP MCP server and custom Authorization header.
Connect your front desk today.
Every integration is included. Every product starts with a 14-day free trial. No card required.
Start your 14-day free trial