How to Use the Casting42 MCP in VS Code Copilot

Q: Can VS Code Copilot pull up specific Casting42 projects?

The editor uses the listcastingprojects tool to read your active slate. You can ask Copilot to generate a summary component based on the current open roles.

Share live casting data across your engineering team with VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Casting42 MCP to VS Code Copilot

Create your Vinkius account to connect Casting42 to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Casting42 with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share Casting42 access in VS Code

Onboarding new developers to a casting application takes too long. By committing your MCP Server config to the repository, everyone gets instant API access. They open Copilot Chat and immediately start querying `list_casting_projects` without hunting for API keys. Finding test data becomes a shared capability. Any engineer on the team can run `search_talents` directly from their editor. The AI client handles the authentication through the centralized Vinkius endpoint token.

Generate types from custom attributes

Keeping frontend types synced with your database schema is a constant battle. Copilot reads your live setup using `list_custom_attributes` and `list_talent_categories`. It writes the TypeScript interfaces based on the actual fields your casting directors created today. Refactoring old code gets much safer. When you ask the agent to update a talent profile component, it knows exactly which tags are currently active via `list_talent_tags`. You avoid pushing code that references deleted database columns.

Integrate talent media into your app

Handling video assets requires knowing the exact payload structure. Your editor calls `list_talent_media` to inspect the real JSON response for headshots and reels. It then writes the exact parsing logic needed to render those assets on screen. Debugging missing images is just a matter of asking a question. Copilot checks `get_talent_details` to verify if a specific actor actually has media attached to their profile. You fix the bug without ever leaving your IDE.

Setup guide

Set up Casting42 MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Casting42 MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Casting42 tools listed. Try asking: "List my recent Casting42 transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "casting42-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Casting42. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Casting42 now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Casting42 MCP in VS Code Copilot

Add a .vscode/mcp.json file to your project repository. Insert your Vinkius server details and commit the file to version control. Every developer who pulls the repo gets immediate access to the tools.

The editor uses the `list_casting_projects` tool to read your active slate. You can ask Copilot to generate a summary component based on the current open roles.

You need version 1.96 or higher. Make sure Copilot Chat is switched to Agent mode so it can execute the tools.

Yes, you can configure it globally instead of per-project. Use the command palette to open the user-level configuration and paste your server details there.

Custom actor fields, headshots, and project details are protected by strict access controls. Vinkius requires a single endpoint token to authenticate the connection. The ephemeral sandbox destroys all context the moment the query finishes.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript