🔌MCP Setup Guide

The Euno AI Assistant can connect to compatible AI clients through the Model Context Protocol (MCP). This lets you explore your data model directly from tools such as Cursor, Claude Desktop, ChatGPT, and other MCP-enabled assistants.

The recommended setup uses OAuth. The first time you use Euno MCP, your client will prompt you to sign in to Euno in a browser. If Euno can identify which persona to use, it will select it automatically. If Euno cannot identify a single clear persona, you will be asked to choose one.

This guide covers the standard direct MCP setup using OAuth.

Prerequisites

Before setting up MCP, make sure you have:

• access to Euno and at least one assigned persona

• an MCP-compatible client such as Cursor, Claude Desktop, ChatGPT (In Developer Mode)or Claude Code in VS Code

Sign In with OAuth

In the recommended OAuth setup, your client will prompt you to sign in to Euno in a browser the first time you connect.

Personas in MCP

Euno MCP uses your active persona to determine what data and actions are available in the session.

• If Euno can identify which persona to use, it will select it automatically.

• This usually happens when you have a default persona, or only one available persona in the relevant account.

• If Euno cannot identify a single clear persona, you will be asked to choose one.

If you have access to more than one persona, you can ask your assistant to show your available personas and switch to another one during the session.

Choose Your Setup

Use the setup mode that matches your client's MCP capabilities:

Use this when	Recommended setup
Your client supports remote HTTP MCP servers	Direct connection
You use Google Gemini Enterprise (Custom MCP Server data store)	Gemini Enterprise Setup
Your client does not support remote HTTP MCP servers, or you prefer a local stdio MCP server	MCP Bridge Setup
Interactive OAuth sign-in is not available, or you prefer manual API key and header configuration	Advanced API Key Setup

Available Tools

Tool	Description
euno_dynamic_instructions	Fetch current Euno MCP instructions, including account-specific metadata guidance
list_personas	Show the personas available in the current session
current_persona	Show the persona currently active for the session
switch_persona	Change the active persona for the session
fetch_single_resource	Retrieve details for a specific resource by URI
find_resource_by_name	Find a resource by name
find_resources_for_topic	Find resources related to a topic or keyword
get_upstream_lineage	Show upstream lineage for a resource
resource_impact_analysis	Show downstream impact for a resource
documentation_search	Search Euno documentation
documentation_get_full_document	Open a full documentation page
documentation_get_surrounding_context	Show the documentation context around a specific chunk
query_to_eql	Turn a natural-language request into an EQL query
fetch_eql_syntax	Show EQL syntax guidance
search_resources_eql	Search resources using an EQL query
count_resources_eql	Count resources matching an EQL query

Catalog Tools

Euno MCP also provides 14 direct catalog tools:

• Glossary: fetch_glossary_term, find_glossary_term, create_glossary_term, update_glossary_term, and delete_glossary_term

• Metadata tags: fetch_metadata_tag, create_metadata_tag, update_metadata_tag, and delete_metadata_tag

• Workflows: fetch_workflow, find_workflow, create_workflow, update_workflow, and delete_workflow

MCP publishes reads as read-only, creates and updates as write operations, and deletes as destructive operations. Your MCP host may use these safety hints to show approval or confirmation UI. Euno still checks your active persona and backend permissions for every call.

All delete tools require confirm=true. Without it, Euno returns a confirmation-required result and does not make the delete request.

Metadata-tag tools are hidden until the tags skill is loaded. Creating or updating a tag is a two-step flow:

1. Call preview_metadata_tag_plan to validate the proposed change without writing it.

2. Pass the returned plan_id to create_metadata_tag or update_metadata_tag, as directed by the preview.

The plan_id receipt is valid for five minutes, can be used only once, and must be used in the same authenticated MCP context. apply_metadata_tag_plan remains available as a deprecated compatibility alias and uses the same receipt.

count_resources_eql can check how many resources match a workflow EQL filter. It does not simulate the complete workflow. Catalog writes are not exposed through the legacy MCP endpoints or the Snowflake batch adapter.

Successful catalog calls return the backend route's JSON shape unchanged. Failures are MCP tool errors with the shared status, error_type, status_code, body_format, and body fields. If status is outcome_unknown, check the current catalog state before deciding whether to retry.

---