4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Nhost MCP Server

Bring Authentication
to CrewAI

Learn how to connect Nhost to CrewAI and start using 15 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Change EmailDelete FileGet FileGet File Presigned UrlGet UserRefresh TokenReset PasswordSignin AnonymousSignin Email PasswordSignin Otp EmailSignin Passwordless EmailSignoutSignup Email PasswordSignup Otp EmailUpload File

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Nhost

What is the Nhost MCP Server?

Connect your Nhost project to any AI agent to manage your backend services through natural language. This server provides a comprehensive interface for Nhost's Authentication and Storage services.

What you can do

  • Authentication Flows — Sign in users via email/password, OTP, magic links, or anonymous sessions using signin_email_password, signin_otp_email, and signin_passwordless_email.
  • User Management — Register new accounts with signup_email_password, retrieve profiles with get_user, and handle password resets or email changes.
  • Session Control — Refresh access tokens and securely sign out users from single or all devices using refresh_token and signout.
  • Cloud Storage — Upload files directly to your Nhost buckets using the upload_file tool, supporting both text and base64 content.

How it works

  1. Subscribe to this server
  2. Provide your Nhost Auth and Storage URLs from your project dashboard
  3. Start managing users and files from Claude, Cursor, or any MCP client

Who is this for?

  • Full-stack Developers — manage user sessions and test auth flows directly from the IDE without switching to the browser.
  • DevOps Engineers — automate user provisioning and file management tasks through simple conversation.
  • Support Teams — quickly verify user profile information and account status to resolve customer issues faster.

Built-in capabilities (15)

change_email

Requires elevated NHOST_JWT credential. Request to change the authenticated user email

delete_file

Permanently delete a file

get_file

Supports optional image transformation parameters. Download the complete file content

get_file_presigned_url

Retrieve a presigned URL for a file

get_user

Requires NHOST_JWT credential. Retrieve the authenticated user profile information

refresh_token

Generate a new JWT access token using a valid refresh token

reset_password

Request a password reset email

signin_anonymous

Create an anonymous user session

signin_email_password

Authenticate a user with email and password

signin_otp_email

Initiate email-based one-time password authentication

signin_passwordless_email

Initiate passwordless authentication by sending a magic link

signout

Invalidate refresh tokens and end the session

signup_email_password

Register a new user account

signup_otp_email

Register a new user account using email OTP

upload_file

Returns metadata for the processed file. Upload a file to a bucket

Why CrewAI?

When paired with CrewAI, Nhost becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Nhost tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Nhost in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Nhost and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Nhost to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Nhost in CrewAI

The Nhost MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 15 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Nhost
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Nhost for CrewAI

Every tool call from CrewAI to the Nhost MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I retrieve the profile of the currently logged-in user?

Use the get_user tool. It fetches the authenticated user's profile information, including their ID and metadata, provided a valid JWT is configured.

02

Is it possible to store documents or images using this server?

Yes. The upload_file action allows you to send raw text or base64 content along with a filename directly to your Nhost Storage bucket.

03

Can I initiate a login without requiring a password?

Absolutely. Use the signin_passwordless_email tool to send a magic link to a user's email address for a seamless passwordless authentication experience.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →