"3D content, models, or technology" matching MCP servers:

Enables AI assistants to write and execute C# code directly inside Autodesk Civil 3D, providing full API access through code generation and execution.

Controls coding agents by enforcing structured implementation plans with PRs and commits as work units, requiring user review at each commit checkpoint to prevent agents from going off track. Includes a visualization dashboard for tracking progress in real-time.

Enables MCP clients to invoke Cursor SDK's agent runtime, run coding agents, list models, and continue conversations.

Provides free, unlimited access to Claude AI models via Puter.js for AI coding agents and IDEs through the MCP protocol.

Enables an orchestrator like Claude Code to hand coding work off to Cursor SDK agents, run as detached background jobs that survive the session and can be listed, inspected, steered, resumed, or stopped. Agents are asynchronous and reusable across follow-up turns, letting expensive frontier models delegate cheaply without blocking or paying to read the results.

Enables AI assistants and MCP clients to launch and manage Cursor Cloud Agents on repositories or without one, select models, follow up mid-run, retrieve or cancel results, and check usage and cost.

Enables MCP clients to run Cursor CLI agent prompts with any model the installed CLI offers, continue existing sessions, and list available models and sessions. Adds guarded execution with concurrency limits, timeouts, cancellation, and operator-gated auto-approval so multiple models can be run in parallel.

Adds a second-opinion advisor to OpenAI Codex CLI, enabling consultation with ChatGPT subscription, OpenAI API, Claude, Gemini, or OpenAI-compatible models during coding sessions.

Enables AI assistants to consult other AI models via OpenRouter for help with coding tasks.

Generates AnyLogic simulation models from natural-language prompts in Claude Code, allowing users to describe queueing systems, factories, or ERs and obtain runnable .alp files.

MCP server for Python build123d to help AIs develop and reason about 3D models and CAD

Add OpenAI (Codex) models to Claude code

MCP server for interacting with a running T3 Code instance. Enables viewing agent threads, sending messages, and approving permission requests from Claude Code or voice-controlled models.

Production-grade, autonomous Model Context Protocol (MCP) server that elevates AI models from stateless code generators into persistent, self-verifying software engineers.

An MCP execution layer that lets capable AI models safely control a developer workstation for file edits, terminal and process execution, Git operations, language-server analysis, browser and Windows UI automation, media processing, job/resource control, and checkpointing. It also coordinates durable single- or multi-agent tasks across providers with leases, dependency graphs, evidence logs, repair loops, and separate verification gates.

Turn the AI you already use into a game studio. Describe a game and Claude or Cursor builds it as a real 3D browser game: playable immediately, hosted on its own link, shareable with anyone. No engine, no build step, no code knowledge, nothing to export. Your AI ships the whole thing: it pulls free 3D assets, rigs characters, and playtests its own build until the game works. Free to start.

Enables coding agents to review GitHub pull requests with a panel of AI models through local or remote MCP endpoints.

Enables Claude Code to research design references per page section across galleries like Awwwards, Dribbble and Mobbin, render the user's page in multiple style directions with live 3D components, and collect votes on a local board. It then produces a PDF report and iteratively builds and refines the actual page, dashboard prototype or mobile screens from that feedback.

Launches the official Codex CLI as a persistent MCP server so DeepSeek Harness can invoke Codex models without storing or transmitting ChatGPT credentials to third parties.

Enables Claude to hand off implementation tasks to OpenAI Codex models running through the Codex CLI, with tools for listing models, delegating work synchronously or in the background, collecting results, and continuing past sessions, while Claude stays the orchestrator that reviews diffs and runs tests.