MCP Integrations
Discover connected MCP servers and assign their tools to Orbitali agents.
MCP integrations are connected in the Orbitali dashboard. The public API can inspect those connections and select which advertised tools an agent may use. Authentication credentials and OAuth tokens remain server-side and are never returned by these endpoints.
All endpoints use API key authentication:
Authorization: Bearer $ORBITALI_API_KEY
Endpoints
| Method | Path | Description |
|---|---|---|
GET | /public/v1/mcp/servers | List the organization's connected MCP servers |
GET | /public/v1/agents/{agent_id}/mcp-tools | List an agent's selected connected MCP tools |
PUT | /public/v1/agents/{agent_id}/mcp-tools | Replace an agent's connected MCP tool selections |
Discover integrations
curl https://api.orbitali.ai/public/v1/mcp/servers \
-H "Authorization: Bearer $ORBITALI_API_KEY"
Each result includes the integration name, status, authentication type, and cached MCP tool
definitions. Only integrations with status: "active" can be assigned. Secret headers, OAuth
tokens, and client credentials are omitted.
Assign tools to an agent
First discover the server ID and exact tool names, then replace the agent's complete MCP tool selection:
curl https://api.orbitali.ai/public/v1/agents/$AGENT_ID/mcp-tools \
-X PUT \
-H "Authorization: Bearer $ORBITALI_API_KEY" \
-H "Content-Type: application/json" \
-d '[
{
"mcpServerId": "40000000-0000-4000-8000-000000000001",
"toolName": "find_available_times",
"enabled": true
},
{
"mcpServerId": "40000000-0000-4000-8000-000000000001",
"toolName": "book_appointment",
"enabled": true
}
]'
PUT replaces all current MCP tool selections. Send [] to clear them. A server from another
organization, an inactive connection, or a tool name not advertised by the integration is rejected.
Read selected tools
curl --fail-with-body "https://api.orbitali.ai/public/v1/agents/$AGENT_ID/mcp-tools" \
-H "Authorization: Bearer $ORBITALI_API_KEY"
GET and PUT return 200 with an array of selections. Each selection has id, agentId, mcpServerId, toolName, and enabled. No selections returns []. The PUT body is an array, not an object containing a tools property. Each item requires mcpServerId (UUID), toolName, and enabled.
The server listing returns an array with id, organizationId, name, url, status, authType, cachedTools, cachedToolsAt, createdAt, and updatedAt, plus optional nativeConnection metadata. Each advertised tool includes its name and input schema. Connections are created/authenticated in the dashboard; these public endpoints do not create connections or refresh their credentials.
Errors
| Status | Code | Recovery |
|---|---|---|
400 | — | Correct invalid UUIDs or selection fields using validation issues. |
400 | MCP_SERVER_UNAVAILABLE | Select an active server belonging to this organization. |
400 | MCP_TOOL_UNAVAILABLE | Rediscover the server's advertised tools and use an exact tool name. |
401 | — | Provide a valid organization API key. |
404 | — | Check the agent ID and its organization. |
Native Plateform integration
In Integrations → Native integrations → Plateform, enter the restaurant slug, Location ID,
and API Hash provided by Plateform. Orbitali validates them and creates a regular MCP connection.
Each native provider can be connected only once per organization through the dashboard.
The Connect Plateform button that opens the connection dialog is disabled when any listed
server has nativeConnection.provider matching the provider's ID, regardless of server status,
or when the provider is unavailable. For an active connection, Replace credentials retains
the connection ID and agent selections; remove the existing connection before connecting again.
Disconnecting removes the stored credentials. To use the same connection on other agents,
assign its tools using the endpoints above.
Create agent is checked by default. After validation and tool discovery succeed, Orbitali creates a draft phone agent with the connection’s tools enabled and opens its instructions. Supply the optional restaurant details (public name, address, regular opening hours and policies) to save stable facts in its static instructions. Availability, date-specific schedules and reservations use live MCP tools. Review the instructions, assign a phone number and activate the agent to receive calls. Uncheck the option to create only the connection. Replacing credentials does not create an agent.
The draft’s identity, instructions and greeting use the dashboard’s current language (English, Spanish or Italian) and never expose internal restaurant slugs or location IDs to callers. During setup, Orbitali calls the advertised MCP timetable tool to retrieve the timezone and the next seven local dates’ booking start times. Retrieval is optional and does not block creation if the timetable is unavailable. Saved slots are labeled with their dates and are never treated as regular opening hours or live availability. The agent checks live tools for each booking. The Plateform API specification does not expose the restaurant’s street address or recurring opening hours; owners supply those facts separately.
For other agents, enable tools explicitly in their MCP panel. Plateform offers:
plateform_check_availability,plateform_get_timetable, andplateform_get_zones;plateform_find_customerandplateform_create_customer;plateform_get_customer_reservationsandplateform_get_reservation;plateform_create_reservation,plateform_edit_reservation, andplateform_cancel_reservation.
Use restaurant-local dates/times and international phone numbers. Verify caller ownership and
confirm changes before editing/cancelling. Customer and booking creation require an explicit privacy
consent value; marketing defaults to false. A pending or unknown booking status is not confirmation.
If a write returns OUTCOME_UNKNOWN, check existing records before retrying.
Native connections appear in the same public listing and support the same tool selection endpoints.
They additionally include optional, non-secret nativeConnection metadata with provider,
restaurantSlug, and locationId. API keys and internal service authentication are never returned.
Orders, receipts, bulk reservation listings, and customer editing are outside the first release.
Native Last.app integration
In Integrations → Native integrations → Last.app, optionally select Create agent and
confirm the restaurant timezone (IANA, for example, Europe/Madrid) and enter restaurant notes, then choose Generate token. Copy the installation token into the
Orbitali integration in your Last.app dashboard. Tokens expire after 30 minutes and are bound
to your Orbitali account. You do not need to find API credentials or location/organization UUIDs.
Keep the dialog open: it detects the installation callback, verifies the restaurant, discovers tools, and completes setup automatically. If you close it after installing, reopen it to resume. Embedding failures preserve the installed account mapping and show a knowledge-specific retry message. Repeated callbacks and completion requests do not create duplicate resources.
Removing the integration in Last.app disables the Orbitali connection. Reinstall with a fresh token. Removing the MCP connection in Orbitali does not uninstall the integration in Last.app; remove it there before reinstalling. Existing agents are not automatically deleted.
API flow: POST /v1/integrations/native/lastapp accepts
{ createAgent?, restaurantDetails?, language?, timezone? } and returns
{ id, status, token, expiresAt }. Store the returned installation ID.
GET /v1/integrations/native/lastapp/:id reads its status; once installed,
POST /v1/integrations/native/lastapp/:id/complete completes setup and returns
{ id, status, expiresAt, agentId? }. GET /v1/integrations/native/lastapp
finds the latest unfinished installed connection for the authenticated account.
All dashboard endpoints require authentication. Customer credential replacement is unsupported.
The public MCP server listing includes only non-secret provider/location metadata:
{ provider: "lastapp", organizationId, locationId }.
Last.app provides lastapp_get_restaurant_info, lastapp_check_availability, lastapp_get_schedules, lastapp_get_zones,
lastapp_find_customers, lastapp_create_customer, lastapp_find_reservations,
lastapp_get_reservation, lastapp_create_reservation, lastapp_update_reservation, and
lastapp_cancel_reservation.
The dialog suggests your browser timezone; confirm it matches the restaurant. The selected timezone is saved with the installation and injected into the generated agent instructions, including daylight saving guidance. The API accepts an optional validated IANA timezone for backwards compatibility; if omitted, add the restaurant timezone to the draft's instructions before activation. Availability and weekly
schedules are local; reservation timestamps must include an explicit UTC offset. Last.app schedules
do not supply a timezone. Searches require an international phone number; reservation searches also
require a date range of at most 31 days. A truncated result is not a complete history.
Customer and reservation creation require explicit privacy consent. Marketing and reservation
notifications default to false. Updates and cancellation require confirmed: true after checking
caller ownership. Last.app's documented response has a cancellation flag but no confirmation state;
non-cancelled reservations report bookingStatus: "unknown" and must not be announced as confirmed.
Use a returned reservation ID for subsequent operations, never a tab ID. After OUTCOME_UNKNOWN,
check existing records before repeating a write.
When Create agent is selected, Orbitali retrieves restaurant information through the integrations service and inserts available name, address, contact details, payment methods and opening hours into the main prompt. Opening hours include explicit dated exceptions and a retrieval timestamp. Kitchen, delivery and reservation schedules are not presented as general opening hours. The generated agent uses the restaurant name when available. Your optional notes supply corrections, policies and timezone.
Optional lookup failures do not block setup; missing information remains unknown and is marked for review. Saved hours are not live booking availability. Existing agents are not rewritten by installation callbacks. The restaurant-info MCP tool can refresh facts when a caller needs current opening information.
Last.app automatic agent creation keeps small restaurant references in the main instructions. When the serialized reference exceeds 7,500 characters, setup saves the full imported snapshot and owner notes as a searchable knowledge document and uses a compact prompt summary. The agent must search knowledge before answering restaurant questions so owner corrections take precedence. Large references require configured knowledge embeddings; ingestion failure aborts setup before saving. The connection, draft agent, tools, and knowledge document are persisted in one transaction. Provider HTTP calls remain inside the integrations service.