Nia MCP access

What the connection shares

MCP is a protocol that lets compatible AI assistants connect to an external service. Ariy’s public gateway can expose a reviewed set of business facts:

• Public business name, description and website
• Services and service areas
• Opening hours and time zone
• Public contact details
• Approved frequently asked questions

The business owner approves which information is published. Private customer records, conversation history, internal instructions and owner controls stay outside this public connection. Review the content itself before approving it; a field labelled “public” can still contain something you did not mean to share.

Connect an assistant

1. Ask Ariy to confirm that public assistant access is enabled for your business and to provide its exact HTTPS endpoint.
2. Review the public business information and which resources should be exposed. Ask Ariy to correct or withdraw anything inaccurate or private before use.
3. In a client that supports remote Streamable HTTP MCP and MCP resources, add the exact endpoint using that client’s current instructions. A client that supports only tools may not show these resources.
4. Test the connection with a harmless request, such as reading the published opening hours. Confirm the business identity and the answer against your approved information.

Endpoint pattern for implementers: https://<confirmed-origin>/api/mcp/<business-handle>. This is a pattern, not a working connection URL. Use the endpoint Ariy confirms for your business; do not guess another business’s handle.

No specific assistant is certified by this page. Available connection menus, plans and resource support vary by client. Never paste Google passwords, calendar tokens or private customer data into public MCP configuration.

Verify the connection

• Initialization succeeds using the confirmed endpoint.
• The resource list contains only the facts your business approved.
• Reading a resource returns your business’s correct public information.
• The tool list is empty for this read-only gateway. That is expected.
• After a published fact changes, have Ariy update the approved public snapshot and repeat the read. Do not assume every internal edit is automatically republished.

These checks should read public facts only. They should not send an enquiry, create a booking, change customer data or consume a paid external action.

Appointments and actions

The current public gateway does not offer conversation, enquiry or calendar tools. Connecting it does not grant an external assistant permission to book, reschedule or cancel appointments. A public resource read is not a conversation with Nia or a confirmed appointment.

For a customer-facing booking page and Google Meet, follow Google Calendar & Meet setup. Native Nia calendar booking has its own account connection and booking configuration. Ask Ariy which actions and clients have been verified for your specific implementation before promising conversational bookings through an assistant.

Troubleshooting

The endpoint does not connect

Check the exact endpoint and ask Ariy to confirm activation. Opening the URL as a normal web page is not a protocol test: the gateway expects MCP requests over HTTP POST. Do not change security settings or add guessed credentials to work around a failed connection.

The client shows no tools

This gateway exposes resources and intentionally has no tools. Confirm that your client can list and read MCP resources.

Information is missing or out of date

Only currently approved resources are available. Ask the business owner or Ariy to review the published snapshot. Disabling access or withdrawing a resource should stop subsequent public reads.

Requests are temporarily limited

Reduce repeated polling and follow the server’s retry guidance. If the problem continues, share the time of the failure and the client’s error with Ariy, with private data and credentials removed.