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
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 reuseSIDECAR_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 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.
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: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
- In Sidecar, select Integrations.
- Open Snowflake, then select the MCP tab.
- Click Enable MCP.
- Paste the service user’s PAT into Service account PAT (organization-wide).
- Click Add server.
- In Integrations → MCP Servers, confirm that Snowflake lists
executesql.
Finish agent setup
Confirm the Snowflake grant and job selection, then verify a query in a new Agent Console run.Verify Agent Console access
- Grant Snowflake to the agent and enable it for the job.
- Create a manual connection-check job, or use an existing manual job whose other setup requirements are complete.
- Replace
<DATA_DATABASE>.<DATA_SCHEMA>.<DATA_TABLE>below with one existing table the service role is allowed to read. Use these job instructions:
- Save the job, make it active, and click Run now to start a new run.
- Complete any required MCP approval.
- 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.
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
The MCP tab says to set up the Snowflake MCP server first
The MCP tab says to set up the Snowflake MCP server first
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.
Connected in Sidecar, but the agent has no Snowflake tools
Connected in Sidecar, but the agent has no Snowflake tools
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.
The PAT is rejected
The PAT is rejected
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.The server initializes, but queries fail
The server initializes, but queries fail
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.