Skip to main content
Enable Snowflake MCP to let Agent Console agents query the data your Snowflake service user can read. Setup is complete when a new Agent Console run executes a Snowflake MCP query successfully. The Agent Console reuses the Snowflake-managed MCP server created during Ask Sidecar admin setup. It connects directly from Anthropic’s infrastructure with an organization-wide service-user PAT. Ask Sidecar uses personal PATs and connects through Sidecar’s proxy.
A personal PAT on the Ask Sidecar tab applies only to that person. The PAT on the MCP tab is shared by Agent Console runs that have access to the server. Use a service user for the Agent Console credential.

Before you start

You need:
  • Account Admin permissions in Sidecar
  • A connected Snowflake integration
  • A verified Snowflake MCP server, following the admin steps in Ask Sidecar with Snowflake query execution
  • A Snowflake administrator who can configure the service user, role grants, and network policy
  • An Agent Console agent with its other setup requirements complete
Sidecar’s setup creates SIDECARMCPSERVER in the PUBLIC schema of your selected Sidecar database. It exposes one executesql tool with Snowflake’s read_only option enabled. See Snowflake’s MCP server guide.

Prepare the service user and role

You can reuse SIDECAR_USER from the Snowflake integration setup. You can also use a separate service user and role with narrower data access. Create that user and role before running the examples below. The examples below use SIDECAR_USER and SIDECAR_ROLE. Replace both names if you use a separate identity. Replace <WAREHOUSE> with the warehouse agents should use, and <MCP_DATABASE> with the database that contains SIDECARMCPSERVER.
Grant the role access to each database, schema, and table agents should query. Replace the placeholders with your approved data scope:
For a view, use GRANT SELECT ON VIEW instead. The PAT’s restricted role needs these grants even if a different role can query the data in Snowsight. A default warehouse and tool discovery do not grant table access.

Configure network access

Snowflake requires service users using PATs to be subject to a network policy with network rules by default. Allow both sources in the effective policy: Check Anthropic’s outbound address documentation before applying the rule. Snowflake’s MCP network guidance explains why remote MCP requests originate from the client provider.
A successful Sidecar connection test does not confirm that Agent Console can connect. Allowing only Sidecar’s IP can leave registration working while the agent has no usable Snowflake tools.
Identify the service user’s effective policy. A user-level policy overrides an account-level policy:
If a policy is already assigned, inspect it:
For a rule-based or new policy, create these rules in the MCP database. Reuse a rule if it already exists and contains the required addresses:
Add both rules to the existing rule-based policy without replacing its other rules. Omit a rule from this statement if it is already in the policy:
If no policy applies, create a dedicated service-user policy and attach it:
Preserve the allowed and blocked rules your organization requires. If you replace a legacy ALLOWED_IP_LIST policy with a rule-based user policy, reproduce its restrictions before attaching the new policy. A user policy overrides the account policy and can block the service user’s other clients.
Use Snowflake’s network policy guide for legacy-policy migration. Do not disable network-policy enforcement to troubleshoot MCP access.

Create the organization PAT

Create a PAT for the service user, restricted to the role prepared above. Choose an expiration allowed by your authentication policy. This example uses 90 days:
Copy the token_secret value from the result. Snowflake shows it only once. Your authentication policy must permit PROGRAMMATIC_ACCESS_TOKEN. See the PAT guide for policy requirements and rotation.

Enable Snowflake MCP in Sidecar

  1. In Sidecar, select Integrations.
  2. Open Snowflake, then select the MCP tab.
  3. Click Enable MCP.
  4. Paste the service user’s PAT into Service account PAT (organization-wide).
  5. Click Add server.
  6. In Integrations → MCP Servers, confirm that Snowflake lists executesql.
Sidecar derives the endpoint from your Snowflake account and selected MCP database. Registration authenticates from Sidecar and discovers tools.

Finish agent setup

Confirm the Snowflake grant and job selection, then verify a query in a new Agent Console run.

Verify Agent Console access

  1. Grant Snowflake to the agent and enable it for the job.
  2. Create a manual connection-check job, or use an existing manual job whose other setup requirements are complete.
  3. Replace <DATA_DATABASE>.<DATA_SCHEMA>.<DATA_TABLE> below with one existing table the service role is allowed to read. Use these job instructions:
  1. Save the job, make it active, and click Run now to start a new run.
  2. Complete any required MCP approval.
  3. In the run transcript, expand the Snowflake tool calls. Confirm that the identity query returns the expected service user, role, and warehouse. Confirm that the table query completes without an access error. An empty table can return zero rows successfully.
Setup is complete when Snowflake MCP executes both queries successfully in Agent Console. A Connected badge or an agent’s written assurance alone does not establish runtime query access.
Grant and job-selection changes apply to new runs. Start a new run after changing them; replying in an existing conversation keeps its captured access. Delete a disposable connection-check job when you finish.

Understand connection checks

The Snowflake Connected badge records earlier authenticated discovery. It can remain Connected after a runtime authentication failure. Check now can advance the check timestamp without validating the credential. Use the runtime verification above before relying on the connection.

Maintain the credential

Rotate the PAT before it expires. In Integrations → MCP Servers, select Replace token on the Snowflake row. After saving the replacement, repeat the Agent Console verification.

Troubleshooting

Complete the MCP object setup on the Ask Sidecar tab. Run the generated SQL and click Verify MCP Server. You do not need a personal Ask Sidecar PAT for Agent Console.
Confirm that Snowflake is selected under the agent’s Settings → Scope → Connected tools and enabled in the job’s MCP servers selection. Start a new run. Check that the service user’s effective network policy allows both Sidecar and Anthropic.MCP authentication can fail during session initialization and leave the agent with no callable Snowflake tools. The agent may describe this as missing provisioning. A Connected badge does not rule out that failure.If it persists, contact support with the Sidecar run URL, timestamp and time zone, and sanitized connection error. Do not send the PAT.
Confirm that the PAT belongs to the intended service user, is not expired or revoked, and is restricted to a role granted to that user. Confirm that the authentication policy permits PROGRAMMATIC_ACCESS_TOKEN and the effective network policy allows both outbound sources. A runtime authentication error alone does not distinguish a bad token from a network-policy rejection.Enter a valid replacement through Replace token, then repeat the Agent Console verification.
Check the service user’s default warehouse and the PAT role’s USAGE on that warehouse. Confirm USAGE on the MCP database, schema, and server, plus USAGE and SELECT on the target data. Tool discovery does not prove these query permissions.