---
title: "Connecting your AI assistant"
description: "Add the Vigilis MCP server to Claude or another MCP client, sign in with your Vigilis account, and confirm the connection is working."
---

> Documentation Index
> Fetch the complete documentation index at: https://support.vigilis.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting your AI assistant

You connect once per assistant. After that, the connection stays signed in and refreshes itself.

## Before you start

- **MCP has to be enabled for your organization.** It is included at Enterprise and is a paid add-on on other tiers. See [What is the Vigilis MCP server](/mcp/what-is-the-mcp-server/).
- **You need your normal Vigilis sign-in.** If your organization requires SSO or MFA, that applies here too. See [Signing in and security](/getting-started/signing-in-and-security/).
- **Your client needs to support remote MCP servers over HTTP.** Older clients that only support local servers cannot connect.

## The server address

```
https://app.mymodero.com/api/mcp/mcp
```

That is the whole configuration. There is no API key, token, or secret to paste. Your client opens a browser window, you sign in to Vigilis, and you approve the connection.

The address is on `mymodero.com` because Vigilis runs on the Modero platform, and that is the address the server itself publishes to your client during setup. The older `app.vigilis.io` form still answers, so an assistant you connected earlier keeps working, but use the address above for anything new. Some clients check that the address you typed matches the one the server publishes, and refuse the connection when it does not.

## Claude Desktop and Claude.ai

1. Open **Settings**, then **Connectors**.
2. Choose **Add custom connector**.
3. Name it `Vigilis` and paste the server address above.
4. Save, then click **Connect**. A browser window opens.
5. Sign in with your Vigilis account and approve the request.

## Claude Code

Run:

```bash
claude mcp add --transport http vigilis https://app.mymodero.com/api/mcp/mcp
```

Then run `/mcp` inside Claude Code and choose to authenticate. A browser window opens for sign-in.

## Other MCP clients

Add the server address as an HTTP or streamable HTTP server and leave the authentication settings at their defaults. The Vigilis server advertises what your client needs during the handshake, so you should not have to enter an authorization URL, client ID, or secret by hand.

One thing to know before you try a less common client: Vigilis approves connections by vendor. Clients from Anthropic (Claude), OpenAI (ChatGPT), and Google (Gemini) are recognized and connect on their own, as are tools running on your own machine that use a local callback address. Anything else, including self-hosted and in-house clients, registers successfully and then waits for a Vigilis administrator to approve it. You are redirected to a pending-approval page naming the client, and until it is approved the sign-in completes but no token is issued, so the connection fails at the last step.

That review is deliberate rather than an obstacle. The consent screen shows a raw client identifier and no vendor name, so you genuinely cannot tell from it where your data would go. Someone who can see the client's registered redirect addresses can.

If you want to use a client outside those three, contact support at [support@vigilis.io](mailto:support@vigilis.io) with the client's name before you set it up, and we will approve it.

## Confirming it worked

A tool list on its own does not prove the connection works, because the list is published before any of your access is checked. Ask for something that needs live data instead, such as how many services are in your inventory, and compare the answer against the [service inventory](/inventory-and-contracts/service-inventory/) page in Vigilis. A real answer means the connection is good end to end.

For what the assistant can do from here, see [What your assistant can do](/mcp/what-your-assistant-can-do/), and [Getting good answers](/mcp/getting-good-answers/) for how to ask.

## If it does not connect

| What you see | What it usually means |
| --- | --- |
| "Not a valid MCP server", or the client says the credentials were rejected, even though sign-in appeared to work | Something between your assistant's vendor and Vigilis is blocking the vendor's request. Sign-in succeeds because it runs in your browser; the connector then calls from the vendor's servers and is refused before it reaches Vigilis. Contact support with the client name and the time it happened. |
| An authorization or invalid token error | Your session expired, or the client is not an approved vendor and is waiting on administrator approval. Reconnect first, and if it repeats, contact support with the client's name. |
| Every tool call says MCP access is not enabled for this organization's plan | Sign-in worked, but the add-on is not on your plan. Confirm it with your Customer Advisor. |
| The sign-in page is branded Modero | Expected. Vigilis runs on the Modero platform and the sign-in window is served from there. Use your normal Vigilis credentials. |
| Sign-in loops back to the sign-in page | Your browser is holding a stale session. Sign out of Vigilis in that browser, close the window, and reconnect from your client. |
| Tools are listed but calls come back refused | The list is the same for everyone and access is checked per call. The refusal names the reason, usually your access level or a module your plan does not include. See [Permissions and security](/mcp/permissions-and-security/). |
| Your client reports the server address does not match the account it was sent to | You are most likely on the older `app.vigilis.io` address. Reconnect using `https://app.mymodero.com/api/mcp/mcp`. |

If none of the above applies, see [Common problems](/troubleshooting/common-problems/) or contact support.

## Common questions

**What is the Vigilis MCP server address?**

https://app.mymodero.com/api/mcp/mcp. Enter that as a remote or HTTP MCP server in your client. There is no separate API key. The older app.vigilis.io form still works for connections made earlier.

**Why does the sign-in page say Modero?**

Vigilis runs on the Modero platform, so the sign-in window is served from app.mymodero.com. Use your normal Vigilis email and password. This is expected.

**How do I know the connection worked?**

A tool list alone does not prove it. Ask a question that needs live data, such as how many services are in your inventory, and check the answer against Vigilis.

**Why do I get an authorization error when I connect?**

A plan problem does not show up here, it shows up on the first tool call. An error at connect time usually means a stale browser session, so sign out of Vigilis and reconnect, or that your client is not one of the recognized vendors and is waiting on approval from Vigilis.

Source: https://support.vigilis.io/mcp/connecting-your-ai-assistant/index.mdx