Euler Developers
  • 🧠 Euler - SVM AI layer
    • Preface
    • πŸ“– Introduction
      • What is the Euler SDK?
      • Euler's Ultimate Vision
      • Target Audience
      • Design Philosophy
    • πŸ—οΈ Euler Stack Architecture
      • Euler AI SVM Chain
      • Euler AI Orchestrator
      • Euler AI Benchmark
      • Euler MCP Layer
      • Model Context Protocol
  • πŸ› οΈ Tutorials
    • Euler AI Benchmark
    • Euler MCP Overview
    • Euler MCP + Claude Desktop
  • Euler MCP + Cursor
  • Euler MCP + Cline
  • Euler MCP + MCP Tester
  • Euler MCP + Code
  • πŸ“… Roadmap
    • Euler Growth Phases
  • πŸ“š References
    • Supported Networks
    • Toolings
    • Euler MCP Resources
Powered by GitBook
On this page
  • What's Cursor
  • Configuring MCP Servers
  • Project Configuration
  • Global Configuration
  • ​Using MCP Tools in Agent

Euler MCP + Cursor

PreviousEuler MCP + Claude DesktopNextEuler MCP + Cline

Last updated 1 month ago

What's Cursor

Cursor is a powerful AI-first code editor that enhances your development workflow. After , you’ll have access to these core features that work together seamlessly to make you more productive:

  • AI-powered code completion that understands your codebase and provides context-aware suggestions

  • Conversation interface for exploring, understanding, and modifying code with Ask, Edit, and Agent modes

  • Intelligent tools for handling complex development tasks

Configuring MCP Servers

The MCP configuration file uses a JSON format with the following structure:

// This example demonstrated an MCP server using the SSE format
// The user should manually setup and run the server
// This could be networked, to allow others to access it too
{
  "mcpServers": {
    "euler-mcp": {
      "url": "https://dev.euler.ai/mcp/sse",
      "env": {}
    }
  }
}

The env field allows you to specify environment variables that will be available to your MCP server process. This is particularly useful for managing API keys and other sensitive configuration.

You can place this configuration in two locations, depending on your use case:

Project Configuration

For tools specific to a project, create a .cursor/mcp.json file in your project directory. This allows you to define MCP servers that are only available within that specific project.

Global Configuration

For tools that you want to use across all projects, create a \~/.cursor/mcp.json file in your home directory. This makes MCP servers available in all your Cursor workspaces.

The Composer Agent will automatically use any MCP tools that are listed under Available Tools on the MCP settings page if it determines them to be relevant. To prompt tool usage intentionally, simply tell the agent to use the tool, referring to it either by name or by description.

By default, when Agent wants to use an MCP tool, it will display a message asking for your approval. You can use the arrow next to the tool name to expand the message, and see what arguments the Agent is calling the tool with.

Configuration Locations

Using MCP Tools in Agent

Tool Approval

Yolo Mode

You can enable Yolo mode to allow Agent to automatically run MCP tools without requiring approval, similar to how terminal commands are executed. Read more about Yolo mode and how to enable it .

installation
​
​
​
​
here
​