Configure Avanoo MCP Proxy (Hosted)

Avanoo MCP Proxy lets you expose approved SaaS services through a single MCP endpoint.

With the hosted deployment, Avanoo manages the proxy infrastructure for you. You only need to configure which services are available and how access should be scoped.

How it works

Setting up a hosted Avanoo MCP Proxy is simple:

1. Select the SaaS services to allow

2. Add scoped instructions for each service

3. Share the MCP Proxy URL with your users

Your users then add that URL to their MCP client, authenticate, and start using the services you exposed.

Before you begin

Make sure you have:

• access to your Avanoo workspace

• permission to configure Avanoo MCP Proxy

• the list of SaaS services you want to expose

Configure the hosted MCP Proxy

Step 1: Select the SaaS services to allow

Choose the SaaS services you want to expose through Avanoo MCP Proxy.

For example:

• Google Drive

• Slack

• Notion

• Jira

• GitHub

Only the services you enable here will be exposed through this MCP Proxy.

Step 2: Add scoped instructions

For each service, you can add instructions to help define the permission scope.

These instructions are used to narrow access. They are not broad behavioral instructions for the assistant.

Use them to specify things such as:

• which workspace, repository, project, or folder should be accessible

• whether access should be read-only or include write actions

• which resources should be excluded

Examples:

Google Drive: only the Product and Support shared drives. Read-only access.

GitHub: only repositories in the avanoo organization. Read-only access to issues, pull requests, and repository content.

Jira: only the ENG and OPS projects. Allow reading tickets and updating ticket status if due date is not in the past.

Keep these instructions short and precise. Their purpose is to define access boundaries for each service.

Step 3: Save the configuration

Once you have selected the services and added the scoped instructions, save the configuration.

Avanoo MCP Proxy is now ready to use.

Step 4: Copy the MCP Proxy URL

Each hosted MCP Proxy is exposed through a single URL.

Example:

https://mcp.avanoo.com/workspaces/<workspace-id>/proxy/<proxy-id>

Share this URL with the users who should access the proxy.

Connect from an MCP client

End users only need the MCP Proxy URL.

To connect:

1. Open the MCP client

2. Add a new MCP server

3. Paste the Avanoo MCP Proxy URL

4. Authenticate when prompted

After authentication, the client can discover and use the SaaS services exposed by that proxy.

What end users need

End users only need:

• the Avanoo MCP Proxy URL

• permission to authenticate

They do not need to:

• configure each SaaS service individually

• manage multiple MCP endpoints

• understand the underlying proxy setup

Update an existing hosted proxy

You can update a hosted MCP Proxy at any time.

Typical updates include:

• adding a new SaaS service

• removing a service

• changing the scoped instructions

• refining access boundaries

Users continue to connect through the same MCP Proxy URL.

Troubleshooting

A service does not appear

Check that:

• the service is enabled in the proxy configuration

• the configuration was saved successfully

• the user authenticated successfully

Access is too broad or too limited

Review the scoped instructions configured for that service.

In most cases, permission issues come from instructions that are too vague or too restrictive.

The user cannot connect

Check that:

• the MCP Proxy URL is correct

• the user is signing in with the correct account

• the user has access to the workspace

Next steps

After your hosted MCP Proxy is configured:

• share the MCP Proxy URL with users

• verify that authentication works from your MCP client

• review the scoped instructions for each enabled service