techprotrade commited on
Commit
cf3884b
·
verified ·
1 Parent(s): 31c9f7d

Add mcps directory (part 2)

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. mcps/grok_com_vercel/tools/list_agent_run_projects.json +47 -0
  2. mcps/grok_com_vercel/tools/list_agent_runs.json +64 -0
  3. mcps/grok_com_vercel/tools/list_deployments.json +31 -0
  4. mcps/grok_com_vercel/tools/list_projects.json +18 -0
  5. mcps/grok_com_vercel/tools/list_teams.json +9 -0
  6. mcps/grok_com_vercel/tools/list_toolbar_threads.json +50 -0
  7. mcps/grok_com_vercel/tools/reply_to_toolbar_thread.json +28 -0
  8. mcps/grok_com_vercel/tools/search_vercel_documentation.json +23 -0
  9. mcps/grok_com_vercel/tools/web_fetch_vercel_url.json +18 -0
  10. mcps/microsoft-learn/tools/microsoft_code_sample_search.json +21 -0
  11. mcps/microsoft-learn/tools/microsoft_docs_fetch.json +16 -0
  12. mcps/microsoft-learn/tools/microsoft_docs_search.json +14 -0
  13. mcps/playwright/tools/browser_click.json +49 -0
  14. mcps/playwright/tools/browser_close.json +10 -0
  15. mcps/playwright/tools/browser_console_messages.json +33 -0
  16. mcps/playwright/tools/browser_drag.json +31 -0
  17. mcps/playwright/tools/browser_drop.json +39 -0
  18. mcps/playwright/tools/browser_evaluate.json +30 -0
  19. mcps/playwright/tools/browser_file_upload.json +18 -0
  20. mcps/playwright/tools/browser_fill_form.json +57 -0
  21. mcps/playwright/tools/browser_handle_dialog.json +22 -0
  22. mcps/playwright/tools/browser_hover.json +22 -0
  23. mcps/playwright/tools/browser_navigate.json +18 -0
  24. mcps/playwright/tools/browser_navigate_back.json +10 -0
  25. mcps/playwright/tools/browser_network_request.json +34 -0
  26. mcps/playwright/tools/browser_network_requests.json +27 -0
  27. mcps/playwright/tools/browser_press_key.json +18 -0
  28. mcps/playwright/tools/browser_resize.json +23 -0
  29. mcps/playwright/tools/browser_run_code_unsafe.json +19 -0
  30. mcps/playwright/tools/browser_select_option.json +30 -0
  31. mcps/playwright/tools/browser_snapshot.json +27 -0
  32. mcps/playwright/tools/browser_tabs.json +32 -0
  33. mcps/playwright/tools/browser_take_screenshot.json +39 -0
  34. mcps/playwright/tools/browser_type.json +35 -0
  35. mcps/playwright/tools/browser_wait_for.json +23 -0
  36. mcps/trigger/tools/cancel_run.json +41 -0
  37. mcps/trigger/tools/create_project_in_org.json +23 -0
  38. mcps/trigger/tools/create_prompt_override.json +54 -0
  39. mcps/trigger/tools/deploy.json +45 -0
  40. mcps/trigger/tools/dev_server_status.json +16 -0
  41. mcps/trigger/tools/get_current_worker.json +34 -0
  42. mcps/trigger/tools/get_prompt_versions.json +41 -0
  43. mcps/trigger/tools/get_query_schema.json +41 -0
  44. mcps/trigger/tools/get_run_details.json +50 -0
  45. mcps/trigger/tools/get_span_details.json +46 -0
  46. mcps/trigger/tools/get_task_schema.json +41 -0
  47. mcps/trigger/tools/initialize_project.json +31 -0
  48. mcps/trigger/tools/list_dashboards.json +34 -0
  49. mcps/trigger/tools/list_deploys.json +68 -0
  50. mcps/trigger/tools/list_orgs.json +9 -0
mcps/grok_com_vercel/tools/list_agent_run_projects.json ADDED
@@ -0,0 +1,47 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_agent_run_projects",
3
+ "description": "List projects in a Vercel team that have Agent Runs observability data, with run counts and average duration rollups. Use this to discover which projects have agent activity before drilling into a project.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "teamId": {
8
+ "type": "string",
9
+ "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
10
+ },
11
+ "environment": {
12
+ "type": "string",
13
+ "description": "Agent run environment, usually \"production\" or \"preview\". Defaults to \"production\"."
14
+ },
15
+ "period": {
16
+ "type": "string",
17
+ "enum": [
18
+ "5m",
19
+ "15m",
20
+ "1h",
21
+ "6h",
22
+ "12h",
23
+ "1d",
24
+ "3d",
25
+ "7d",
26
+ "14d",
27
+ "30d",
28
+ "90d"
29
+ ],
30
+ "description": "Preset time range. Ignored when both from and to are provided. Defaults to the dashboard endpoint default."
31
+ },
32
+ "from": {
33
+ "type": "string",
34
+ "description": "Start time as ISO 8601, Unix seconds, Unix milliseconds, or a relative duration like \"12h\". Must be used with to."
35
+ },
36
+ "to": {
37
+ "type": "string",
38
+ "description": "End time as ISO 8601, Unix seconds, Unix milliseconds, a relative duration like \"1h\", or \"now\". Must be used with from."
39
+ }
40
+ },
41
+ "required": [
42
+ "teamId"
43
+ ],
44
+ "additionalProperties": false,
45
+ "$schema": "http://json-schema.org/draft-07/schema#"
46
+ }
47
+ }
mcps/grok_com_vercel/tools/list_agent_runs.json ADDED
@@ -0,0 +1,64 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_agent_runs",
3
+ "description": "List Agent Runs for a Vercel project, including summaries, status, model, trigger, token usage, time series, and pagination metadata. Use this to find recent or matching production agent runs before fetching detail or trace data.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "teamId": {
8
+ "type": "string",
9
+ "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
10
+ },
11
+ "projectId": {
12
+ "type": "string",
13
+ "description": "The project ID to get the deployment events for. Alternatively the project slug can be used.\nProject IDs start with \"prj_\".\nIf you do not know the project ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the projectId\n- Use the `list_projects` tool"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "description": "Agent run environment, usually \"production\" or \"preview\". Defaults to \"production\"."
18
+ },
19
+ "period": {
20
+ "type": "string",
21
+ "enum": [
22
+ "5m",
23
+ "15m",
24
+ "1h",
25
+ "6h",
26
+ "12h",
27
+ "1d",
28
+ "3d",
29
+ "7d",
30
+ "14d",
31
+ "30d",
32
+ "90d"
33
+ ],
34
+ "description": "Preset time range. Ignored when both from and to are provided. Defaults to the dashboard endpoint default."
35
+ },
36
+ "from": {
37
+ "type": "string",
38
+ "description": "Start time as ISO 8601, Unix seconds, Unix milliseconds, or a relative duration like \"12h\". Must be used with to."
39
+ },
40
+ "to": {
41
+ "type": "string",
42
+ "description": "End time as ISO 8601, Unix seconds, Unix milliseconds, a relative duration like \"1h\", or \"now\". Must be used with from."
43
+ },
44
+ "page": {
45
+ "type": "number",
46
+ "description": "1-based page number. Defaults to 1."
47
+ },
48
+ "pageSize": {
49
+ "type": "number",
50
+ "description": "Number of runs per page. The dashboard endpoint caps this at 100."
51
+ },
52
+ "search": {
53
+ "type": "string",
54
+ "description": "Server-side title search for Agent Runs."
55
+ }
56
+ },
57
+ "required": [
58
+ "teamId",
59
+ "projectId"
60
+ ],
61
+ "additionalProperties": false,
62
+ "$schema": "http://json-schema.org/draft-07/schema#"
63
+ }
64
+ }
mcps/grok_com_vercel/tools/list_deployments.json ADDED
@@ -0,0 +1,31 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_deployments",
3
+ "description": "List all deployments for a project",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectId": {
8
+ "type": "string",
9
+ "description": "The project ID to list deployments for."
10
+ },
11
+ "teamId": {
12
+ "type": "string",
13
+ "description": "The team ID to list deployments for."
14
+ },
15
+ "since": {
16
+ "type": "number",
17
+ "description": "Get deployments created after this timestamp."
18
+ },
19
+ "until": {
20
+ "type": "number",
21
+ "description": "Get deployments created before this timestamp."
22
+ }
23
+ },
24
+ "required": [
25
+ "projectId",
26
+ "teamId"
27
+ ],
28
+ "additionalProperties": false,
29
+ "$schema": "http://json-schema.org/draft-07/schema#"
30
+ }
31
+ }
mcps/grok_com_vercel/tools/list_projects.json ADDED
@@ -0,0 +1,18 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_projects",
3
+ "description": "List all Vercel projects for a user (with a max of 50). Use this to help discover the Project ID of the project that the user is working on.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "teamId": {
8
+ "type": "string",
9
+ "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
10
+ }
11
+ },
12
+ "required": [
13
+ "teamId"
14
+ ],
15
+ "additionalProperties": false,
16
+ "$schema": "http://json-schema.org/draft-07/schema#"
17
+ }
18
+ }
mcps/grok_com_vercel/tools/list_teams.json ADDED
@@ -0,0 +1,9 @@
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_teams",
3
+ "description": "List the user's teams. Use this to help discover the Team ID of the teams that the user is part of.",
4
+ "inputSchema": {
5
+ "$schema": "http://json-schema.org/draft-07/schema#",
6
+ "type": "object",
7
+ "properties": {}
8
+ }
9
+ }
mcps/grok_com_vercel/tools/list_toolbar_threads.json ADDED
@@ -0,0 +1,50 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_toolbar_threads",
3
+ "description": "List Vercel toolbar comment threads for a team. Returns unresolved threads by default. Use this to see feedback, comments, or discussions on deployments and previews.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "teamId": {
8
+ "type": "string",
9
+ "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
10
+ },
11
+ "projectId": {
12
+ "type": "string",
13
+ "description": "Filter by project ID"
14
+ },
15
+ "branch": {
16
+ "type": "string",
17
+ "description": "Filter by branch name"
18
+ },
19
+ "status": {
20
+ "type": "string",
21
+ "enum": [
22
+ "resolved",
23
+ "unresolved"
24
+ ],
25
+ "description": "Filter by status. Defaults to unresolved."
26
+ },
27
+ "page": {
28
+ "type": "string",
29
+ "description": "Filter by page path (e.g. /docs) or glob (e.g. /docs*)"
30
+ },
31
+ "search": {
32
+ "type": "string",
33
+ "description": "Search text in comments"
34
+ },
35
+ "limit": {
36
+ "type": "number",
37
+ "description": "Maximum number of results to return. Defaults to 20."
38
+ },
39
+ "offset": {
40
+ "type": "number",
41
+ "description": "Pagination offset"
42
+ }
43
+ },
44
+ "required": [
45
+ "teamId"
46
+ ],
47
+ "additionalProperties": false,
48
+ "$schema": "http://json-schema.org/draft-07/schema#"
49
+ }
50
+ }
mcps/grok_com_vercel/tools/reply_to_toolbar_thread.json ADDED
@@ -0,0 +1,28 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "reply_to_toolbar_thread",
3
+ "description": "Add a reply message to an existing toolbar thread.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "threadId": {
8
+ "type": "string",
9
+ "description": "The thread ID to reply to"
10
+ },
11
+ "teamId": {
12
+ "type": "string",
13
+ "description": "The team ID to get the deployment events for. Alternatively the team slug can be used.\nTeam IDs start with \"team_\".\nIf you do not know the team ID or slug, it can be found through these mechanism:\n- Read the file .vercel/project.json if it exists and extract the orgId\n- Use the `list_teams` tool"
14
+ },
15
+ "markdown": {
16
+ "type": "string",
17
+ "description": "The message content in markdown format"
18
+ }
19
+ },
20
+ "required": [
21
+ "threadId",
22
+ "teamId",
23
+ "markdown"
24
+ ],
25
+ "additionalProperties": false,
26
+ "$schema": "http://json-schema.org/draft-07/schema#"
27
+ }
28
+ }
mcps/grok_com_vercel/tools/search_vercel_documentation.json ADDED
@@ -0,0 +1,23 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "search_vercel_documentation",
3
+ "description": "Search the Vercel documentation.\n \n Use this tool to answer any questions about Vercel’s platform, features, and best practices, including:\n - Core Concepts: Projects, Deployments, Git Integration, Preview Deployments, Environments\n - Frontend & Frameworks: Next.js, SvelteKit, Nuxt, Astro, Remix, frameworks configuration and optimization\n - APIs: REST API, Vercel SDK, Build Output API\n - Compute: Fluid Compute, Functions, Routing Middleware, Cron Jobs, OG Image Generation, Sandbox, Data Cache\n - AI: Vercel AI SDK, AI Gateway, MCP, v0\n - Performance & Delivery: Edge Network, Caching, CDN, Image Optimization, Headers, Redirects, Rewrites\n - Pricing: Plans, Spend Management, Billing\n - Security: Audit Logs, Firewall, Bot Management, BotID, OIDC, RBAC, Secure Compute, 2FA\n - Storage: Blog, Edge Config",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "topic": {
8
+ "type": "string",
9
+ "description": "Topic to focus the documentation search on (e.g., 'routing', 'data-fetching')."
10
+ },
11
+ "tokens": {
12
+ "type": "number",
13
+ "description": "Maximum number of tokens to include in the result. Default is 2500.",
14
+ "default": 2500
15
+ }
16
+ },
17
+ "required": [
18
+ "topic"
19
+ ],
20
+ "additionalProperties": false,
21
+ "$schema": "http://json-schema.org/draft-07/schema#"
22
+ }
23
+ }
mcps/grok_com_vercel/tools/web_fetch_vercel_url.json ADDED
@@ -0,0 +1,18 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "web_fetch_vercel_url",
3
+ "description": "Fetches a Vercel deployment URL and returns the response.\n This is useful if another web fetch tool returns 401 (Unauthorized) or 403 (Forbidden) for a Vercel URL.\n Supports accessing deployments protected with Vercel Authentication which the user of this MCP server has access to.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "url": {
8
+ "type": "string",
9
+ "description": "The full URL of the Vercel deployment including the path (e.g. \"https://myapp.vercel.app/my-page\")."
10
+ }
11
+ },
12
+ "required": [
13
+ "url"
14
+ ],
15
+ "additionalProperties": false,
16
+ "$schema": "http://json-schema.org/draft-07/schema#"
17
+ }
18
+ }
mcps/microsoft-learn/tools/microsoft_code_sample_search.json ADDED
@@ -0,0 +1,21 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "microsoft_code_sample_search",
3
+ "description": "Search for code snippets and examples in official Microsoft Learn documentation. This tool retrieves relevant code samples from Microsoft documentation pages providing developers with practical implementation examples and best practices for Microsoft/Azure products and services related coding tasks. This tool will help you use the **LATEST OFFICIAL** code snippets to empower coding capabilities.\n\n## When to Use This Tool\n- When you are going to provide sample Microsoft/Azure related code snippets in your answers.\n- When you are **generating any Microsoft/Azure related code**.\n\n## Usage Pattern\nInput a descriptive query, or SDK/class/method name to retrieve related code samples. The optional parameter `language` can help to filter results.\n\nEligible values for `language` parameter include: csharp javascript typescript python powershell azurecli al sql java kusto cpp go rust ruby php",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "query": {
8
+ "description": "a descriptive query, SDK name, method name or code snippet related to Microsoft/Azure products, services, platforms, developer tools, frameworks, APIs or SDKs",
9
+ "type": "string"
10
+ },
11
+ "language": {
12
+ "description": "Optional parameter specifying the programming language of code snippets to retrieve. Can significantly improve search quality if provided. Eligible values: csharp javascript typescript python powershell azurecli al sql java kusto cpp go rust ruby php",
13
+ "type": "string",
14
+ "default": null
15
+ }
16
+ },
17
+ "required": [
18
+ "query"
19
+ ]
20
+ }
21
+ }
mcps/microsoft-learn/tools/microsoft_docs_fetch.json ADDED
@@ -0,0 +1,16 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "microsoft_docs_fetch",
3
+ "description": "Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies.\n\n## When to Use This Tool\n- When search results provide incomplete information or truncated content\n- When you need complete step-by-step procedures or tutorials\n- When you need troubleshooting sections, prerequisites, or detailed explanations\n- When search results reference a specific page that seems highly relevant\n- For comprehensive guides that require full context\n\n## Usage Pattern\nUse this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture.\n\n## URL Requirements\n- The URL must be a valid HTML documentation webpage from the microsoft.com domain\n- Binary files (PDF, DOCX, images, etc.) are not supported\n\n## Output Format\nmarkdown with headings, code blocks, tables, and links preserved.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "url": {
8
+ "description": "URL of the Microsoft documentation page to read",
9
+ "type": "string"
10
+ }
11
+ },
12
+ "required": [
13
+ "url"
14
+ ]
15
+ }
16
+ }
mcps/microsoft-learn/tools/microsoft_docs_search.json ADDED
@@ -0,0 +1,14 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "microsoft_docs_search",
3
+ "description": "Search official Microsoft/Azure documentation to find the most relevant and trustworthy content for a user's query. This tool returns up to 10 high-quality content chunks (each max 500 tokens), extracted from Microsoft Learn and other official sources. Each result includes the article title, URL, and a self-contained content excerpt optimized for fast retrieval and reasoning. Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge.\n\n## Follow-up Pattern\nTo ensure completeness, use microsoft_docs_fetch when high-value pages are identified by search. The fetch tool complements search by providing the full detail. This is a required step for comprehensive results.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "query": {
8
+ "description": "a query or topic about Microsoft/Azure products, services, platforms, developer tools, frameworks, or APIs",
9
+ "type": "string",
10
+ "default": null
11
+ }
12
+ }
13
+ }
14
+ }
mcps/playwright/tools/browser_click.json ADDED
@@ -0,0 +1,49 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_click",
3
+ "description": "Perform click on a web page",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "element": {
9
+ "description": "Human-readable element description used to obtain permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "target": {
13
+ "type": "string",
14
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
15
+ },
16
+ "doubleClick": {
17
+ "description": "Whether to perform a double click instead of a single click",
18
+ "type": "boolean"
19
+ },
20
+ "button": {
21
+ "description": "Button to click, defaults to left",
22
+ "type": "string",
23
+ "enum": [
24
+ "left",
25
+ "right",
26
+ "middle"
27
+ ]
28
+ },
29
+ "modifiers": {
30
+ "description": "Modifier keys to press",
31
+ "type": "array",
32
+ "items": {
33
+ "type": "string",
34
+ "enum": [
35
+ "Alt",
36
+ "Control",
37
+ "ControlOrMeta",
38
+ "Meta",
39
+ "Shift"
40
+ ]
41
+ }
42
+ }
43
+ },
44
+ "required": [
45
+ "target"
46
+ ],
47
+ "additionalProperties": false
48
+ }
49
+ }
mcps/playwright/tools/browser_close.json ADDED
@@ -0,0 +1,10 @@
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_close",
3
+ "description": "Close the page",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {},
8
+ "additionalProperties": false
9
+ }
10
+ }
mcps/playwright/tools/browser_console_messages.json ADDED
@@ -0,0 +1,33 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_console_messages",
3
+ "description": "Returns all console messages",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "level": {
9
+ "default": "info",
10
+ "description": "Level of the console messages to return. Each level includes the messages of more severe levels. Defaults to \"info\".",
11
+ "type": "string",
12
+ "enum": [
13
+ "error",
14
+ "warning",
15
+ "info",
16
+ "debug"
17
+ ]
18
+ },
19
+ "all": {
20
+ "description": "Return all console messages since the beginning of the session, not just since the last navigation. Defaults to false.",
21
+ "type": "boolean"
22
+ },
23
+ "filename": {
24
+ "description": "Filename to save the console messages to. If not provided, messages are returned as text.",
25
+ "type": "string"
26
+ }
27
+ },
28
+ "required": [
29
+ "level"
30
+ ],
31
+ "additionalProperties": false
32
+ }
33
+ }
mcps/playwright/tools/browser_drag.json ADDED
@@ -0,0 +1,31 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_drag",
3
+ "description": "Perform drag and drop between two elements",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "startElement": {
9
+ "description": "Human-readable source element description used to obtain the permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "startTarget": {
13
+ "type": "string",
14
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
15
+ },
16
+ "endElement": {
17
+ "description": "Human-readable target element description used to obtain the permission to interact with the element",
18
+ "type": "string"
19
+ },
20
+ "endTarget": {
21
+ "type": "string",
22
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
23
+ }
24
+ },
25
+ "required": [
26
+ "startTarget",
27
+ "endTarget"
28
+ ],
29
+ "additionalProperties": false
30
+ }
31
+ }
mcps/playwright/tools/browser_drop.json ADDED
@@ -0,0 +1,39 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_drop",
3
+ "description": "Drop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of \"paths\" or \"data\" must be provided.",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "element": {
9
+ "description": "Human-readable element description used to obtain permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "target": {
13
+ "type": "string",
14
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
15
+ },
16
+ "paths": {
17
+ "description": "Absolute paths to files to drop onto the element.",
18
+ "type": "array",
19
+ "items": {
20
+ "type": "string"
21
+ }
22
+ },
23
+ "data": {
24
+ "description": "Data to drop, as a map of MIME type to string value (e.g. {\"text/plain\": \"hello\", \"text/uri-list\": \"https://example.com\"}).",
25
+ "type": "object",
26
+ "propertyNames": {
27
+ "type": "string"
28
+ },
29
+ "additionalProperties": {
30
+ "type": "string"
31
+ }
32
+ }
33
+ },
34
+ "required": [
35
+ "target"
36
+ ],
37
+ "additionalProperties": false
38
+ }
39
+ }
mcps/playwright/tools/browser_evaluate.json ADDED
@@ -0,0 +1,30 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_evaluate",
3
+ "description": "Evaluate JavaScript expression on page or element",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "element": {
9
+ "description": "Human-readable element description used to obtain permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "target": {
13
+ "description": "Exact target element reference from the page snapshot, or a unique element selector",
14
+ "type": "string"
15
+ },
16
+ "function": {
17
+ "type": "string",
18
+ "description": "() => { /* code */ } or (element) => { /* code */ } when element is provided"
19
+ },
20
+ "filename": {
21
+ "description": "Filename to save the result to. If not provided, result is returned as text.",
22
+ "type": "string"
23
+ }
24
+ },
25
+ "required": [
26
+ "function"
27
+ ],
28
+ "additionalProperties": false
29
+ }
30
+ }
mcps/playwright/tools/browser_file_upload.json ADDED
@@ -0,0 +1,18 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_file_upload",
3
+ "description": "Upload one or multiple files",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "paths": {
9
+ "description": "The absolute paths to the files to upload. Can be single file or multiple files. If omitted, file chooser is cancelled.",
10
+ "type": "array",
11
+ "items": {
12
+ "type": "string"
13
+ }
14
+ }
15
+ },
16
+ "additionalProperties": false
17
+ }
18
+ }
mcps/playwright/tools/browser_fill_form.json ADDED
@@ -0,0 +1,57 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_fill_form",
3
+ "description": "Fill multiple form fields",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "fields": {
9
+ "type": "array",
10
+ "items": {
11
+ "type": "object",
12
+ "properties": {
13
+ "element": {
14
+ "description": "Human-readable element description used to obtain permission to interact with the element",
15
+ "type": "string"
16
+ },
17
+ "target": {
18
+ "type": "string",
19
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
20
+ },
21
+ "name": {
22
+ "type": "string",
23
+ "description": "Human-readable field name"
24
+ },
25
+ "type": {
26
+ "type": "string",
27
+ "enum": [
28
+ "textbox",
29
+ "checkbox",
30
+ "radio",
31
+ "combobox",
32
+ "slider"
33
+ ],
34
+ "description": "Type of the field"
35
+ },
36
+ "value": {
37
+ "type": "string",
38
+ "description": "Value to fill in the field. If the field is a checkbox, the value should be `true` or `false`. If the field is a combobox, the value should be the text of the option."
39
+ }
40
+ },
41
+ "required": [
42
+ "target",
43
+ "name",
44
+ "type",
45
+ "value"
46
+ ],
47
+ "additionalProperties": false
48
+ },
49
+ "description": "Fields to fill in"
50
+ }
51
+ },
52
+ "required": [
53
+ "fields"
54
+ ],
55
+ "additionalProperties": false
56
+ }
57
+ }
mcps/playwright/tools/browser_handle_dialog.json ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_handle_dialog",
3
+ "description": "Handle a dialog",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "accept": {
9
+ "type": "boolean",
10
+ "description": "Whether to accept the dialog."
11
+ },
12
+ "promptText": {
13
+ "description": "The text of the prompt in case of a prompt dialog.",
14
+ "type": "string"
15
+ }
16
+ },
17
+ "required": [
18
+ "accept"
19
+ ],
20
+ "additionalProperties": false
21
+ }
22
+ }
mcps/playwright/tools/browser_hover.json ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_hover",
3
+ "description": "Hover over element on page",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "element": {
9
+ "description": "Human-readable element description used to obtain permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "target": {
13
+ "type": "string",
14
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
15
+ }
16
+ },
17
+ "required": [
18
+ "target"
19
+ ],
20
+ "additionalProperties": false
21
+ }
22
+ }
mcps/playwright/tools/browser_navigate.json ADDED
@@ -0,0 +1,18 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_navigate",
3
+ "description": "Navigate to a URL",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "url": {
9
+ "type": "string",
10
+ "description": "The URL to navigate to"
11
+ }
12
+ },
13
+ "required": [
14
+ "url"
15
+ ],
16
+ "additionalProperties": false
17
+ }
18
+ }
mcps/playwright/tools/browser_navigate_back.json ADDED
@@ -0,0 +1,10 @@
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_navigate_back",
3
+ "description": "Go back to the previous page in the history",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {},
8
+ "additionalProperties": false
9
+ }
10
+ }
mcps/playwright/tools/browser_network_request.json ADDED
@@ -0,0 +1,34 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_network_request",
3
+ "description": "Returns full details (headers and body) of a single network request, or a single part if `part` is set. Use the number from browser_network_requests.",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "index": {
9
+ "type": "integer",
10
+ "minimum": 1,
11
+ "maximum": 9007199254740991,
12
+ "description": "1-based index of the request, as printed by browser_network_requests."
13
+ },
14
+ "part": {
15
+ "description": "Return only this part of the request. Omit to return full details.",
16
+ "type": "string",
17
+ "enum": [
18
+ "request-headers",
19
+ "request-body",
20
+ "response-headers",
21
+ "response-body"
22
+ ]
23
+ },
24
+ "filename": {
25
+ "description": "Filename to save the result to. If not provided, output is returned as text.",
26
+ "type": "string"
27
+ }
28
+ },
29
+ "required": [
30
+ "index"
31
+ ],
32
+ "additionalProperties": false
33
+ }
34
+ }
mcps/playwright/tools/browser_network_requests.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_network_requests",
3
+ "description": "Returns a numbered list of network requests since loading the page. Use browser_network_request with the number to get full details.",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "static": {
9
+ "default": false,
10
+ "description": "Whether to include successful static resources like images, fonts, scripts, etc. Defaults to false.",
11
+ "type": "boolean"
12
+ },
13
+ "filter": {
14
+ "description": "Only return requests whose URL matches this regexp (e.g. \"/api/.*user\").",
15
+ "type": "string"
16
+ },
17
+ "filename": {
18
+ "description": "Filename to save the network requests to. If not provided, requests are returned as text.",
19
+ "type": "string"
20
+ }
21
+ },
22
+ "required": [
23
+ "static"
24
+ ],
25
+ "additionalProperties": false
26
+ }
27
+ }
mcps/playwright/tools/browser_press_key.json ADDED
@@ -0,0 +1,18 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_press_key",
3
+ "description": "Press a key on the keyboard",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "key": {
9
+ "type": "string",
10
+ "description": "Name of the key to press or a character to generate, such as `ArrowLeft` or `a`"
11
+ }
12
+ },
13
+ "required": [
14
+ "key"
15
+ ],
16
+ "additionalProperties": false
17
+ }
18
+ }
mcps/playwright/tools/browser_resize.json ADDED
@@ -0,0 +1,23 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_resize",
3
+ "description": "Resize the browser window",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "width": {
9
+ "type": "number",
10
+ "description": "Width of the browser window"
11
+ },
12
+ "height": {
13
+ "type": "number",
14
+ "description": "Height of the browser window"
15
+ }
16
+ },
17
+ "required": [
18
+ "width",
19
+ "height"
20
+ ],
21
+ "additionalProperties": false
22
+ }
23
+ }
mcps/playwright/tools/browser_run_code_unsafe.json ADDED
@@ -0,0 +1,19 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_run_code_unsafe",
3
+ "description": "Run a Playwright code snippet. Unsafe: executes arbitrary JavaScript in the Playwright server process and is RCE-equivalent.",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "code": {
9
+ "description": "A JavaScript function containing Playwright code to execute. It will be invoked with a single argument, page, which you can use for any page interaction. For example: `async (page) => { await page.getByRole('button', { name: 'Submit' }).click(); return await page.title(); }`",
10
+ "type": "string"
11
+ },
12
+ "filename": {
13
+ "description": "Load code from the specified file. If both code and filename are provided, code will be ignored.",
14
+ "type": "string"
15
+ }
16
+ },
17
+ "additionalProperties": false
18
+ }
19
+ }
mcps/playwright/tools/browser_select_option.json ADDED
@@ -0,0 +1,30 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_select_option",
3
+ "description": "Select an option in a dropdown",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "element": {
9
+ "description": "Human-readable element description used to obtain permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "target": {
13
+ "type": "string",
14
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
15
+ },
16
+ "values": {
17
+ "type": "array",
18
+ "items": {
19
+ "type": "string"
20
+ },
21
+ "description": "Array of values to select in the dropdown. This can be a single value or multiple values."
22
+ }
23
+ },
24
+ "required": [
25
+ "target",
26
+ "values"
27
+ ],
28
+ "additionalProperties": false
29
+ }
30
+ }
mcps/playwright/tools/browser_snapshot.json ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_snapshot",
3
+ "description": "Capture accessibility snapshot of the current page, this is better than screenshot",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "target": {
9
+ "description": "Exact target element reference from the page snapshot, or a unique element selector",
10
+ "type": "string"
11
+ },
12
+ "filename": {
13
+ "description": "Save snapshot to markdown file instead of returning it in the response.",
14
+ "type": "string"
15
+ },
16
+ "depth": {
17
+ "description": "Limit the depth of the snapshot tree",
18
+ "type": "number"
19
+ },
20
+ "boxes": {
21
+ "description": "Include each element's bounding box as [box=x,y,width,height] in the snapshot. Coordinates are viewport-relative, in CSS pixels (Element.getBoundingClientRect)",
22
+ "type": "boolean"
23
+ }
24
+ },
25
+ "additionalProperties": false
26
+ }
27
+ }
mcps/playwright/tools/browser_tabs.json ADDED
@@ -0,0 +1,32 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_tabs",
3
+ "description": "List, create, close, or select a browser tab.",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "action": {
9
+ "type": "string",
10
+ "enum": [
11
+ "list",
12
+ "new",
13
+ "close",
14
+ "select"
15
+ ],
16
+ "description": "Operation to perform"
17
+ },
18
+ "index": {
19
+ "description": "Tab index, used for close/select. If omitted for close, current tab is closed.",
20
+ "type": "number"
21
+ },
22
+ "url": {
23
+ "description": "URL to navigate to in the new tab, used for new.",
24
+ "type": "string"
25
+ }
26
+ },
27
+ "required": [
28
+ "action"
29
+ ],
30
+ "additionalProperties": false
31
+ }
32
+ }
mcps/playwright/tools/browser_take_screenshot.json ADDED
@@ -0,0 +1,39 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_take_screenshot",
3
+ "description": "Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions.",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "element": {
9
+ "description": "Human-readable element description used to obtain permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "target": {
13
+ "description": "Exact target element reference from the page snapshot, or a unique element selector",
14
+ "type": "string"
15
+ },
16
+ "type": {
17
+ "default": "png",
18
+ "description": "Image format for the screenshot. Default is png.",
19
+ "type": "string",
20
+ "enum": [
21
+ "png",
22
+ "jpeg"
23
+ ]
24
+ },
25
+ "filename": {
26
+ "description": "File name to save the screenshot to. Defaults to `page-{timestamp}.{png|jpeg}` if not specified. Prefer relative file names to stay within the output directory.",
27
+ "type": "string"
28
+ },
29
+ "fullPage": {
30
+ "description": "When true, takes a screenshot of the full scrollable page, instead of the currently visible viewport. Cannot be used with element screenshots.",
31
+ "type": "boolean"
32
+ }
33
+ },
34
+ "required": [
35
+ "type"
36
+ ],
37
+ "additionalProperties": false
38
+ }
39
+ }
mcps/playwright/tools/browser_type.json ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_type",
3
+ "description": "Type text into editable element",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "element": {
9
+ "description": "Human-readable element description used to obtain permission to interact with the element",
10
+ "type": "string"
11
+ },
12
+ "target": {
13
+ "type": "string",
14
+ "description": "Exact target element reference from the page snapshot, or a unique element selector"
15
+ },
16
+ "text": {
17
+ "type": "string",
18
+ "description": "Text to type into the element"
19
+ },
20
+ "submit": {
21
+ "description": "Whether to submit entered text (press Enter after)",
22
+ "type": "boolean"
23
+ },
24
+ "slowly": {
25
+ "description": "Whether to type one character at a time. Useful for triggering key handlers in the page. By default entire text is filled in at once.",
26
+ "type": "boolean"
27
+ }
28
+ },
29
+ "required": [
30
+ "target",
31
+ "text"
32
+ ],
33
+ "additionalProperties": false
34
+ }
35
+ }
mcps/playwright/tools/browser_wait_for.json ADDED
@@ -0,0 +1,23 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "browser_wait_for",
3
+ "description": "Wait for text to appear or disappear or a specified time to pass",
4
+ "inputSchema": {
5
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
6
+ "type": "object",
7
+ "properties": {
8
+ "time": {
9
+ "description": "The time to wait in seconds",
10
+ "type": "number"
11
+ },
12
+ "text": {
13
+ "description": "The text to wait for",
14
+ "type": "string"
15
+ },
16
+ "textGone": {
17
+ "description": "The text to wait for to disappear",
18
+ "type": "string"
19
+ }
20
+ },
21
+ "additionalProperties": false
22
+ }
23
+ }
mcps/trigger/tools/cancel_run.json ADDED
@@ -0,0 +1,41 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "cancel_run",
3
+ "description": "Cancel a run. The run ID is the ID of the run that was triggered. It starts with run_",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ },
30
+ "runId": {
31
+ "type": "string",
32
+ "description": "The ID of the run to get the details of, starts with run_"
33
+ }
34
+ },
35
+ "required": [
36
+ "runId"
37
+ ],
38
+ "additionalProperties": false,
39
+ "$schema": "http://json-schema.org/draft-07/schema#"
40
+ }
41
+ }
mcps/trigger/tools/create_project_in_org.json ADDED
@@ -0,0 +1,23 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "create_project_in_org",
3
+ "description": "Create a new project in an organization. Only do this if the user wants to add Trigger.dev to an existing project. If there is already a trigger.config.ts file present, then you should not create a new project.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "orgParam": {
8
+ "type": "string",
9
+ "description": "The organization to create the project in, can either be the organization slug or the ID. Use the list_orgs tool to get a list of organizations and ask the user to select one."
10
+ },
11
+ "name": {
12
+ "type": "string",
13
+ "description": "The name of the project to create."
14
+ }
15
+ },
16
+ "required": [
17
+ "orgParam",
18
+ "name"
19
+ ],
20
+ "additionalProperties": false,
21
+ "$schema": "http://json-schema.org/draft-07/schema#"
22
+ }
23
+ }
mcps/trigger/tools/create_prompt_override.json ADDED
@@ -0,0 +1,54 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "create_prompt_override",
3
+ "description": "Create a dashboard override for a prompt. The override takes precedence over the current code version when resolving the prompt. Provide the full text content for the override.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ },
30
+ "slug": {
31
+ "type": "string",
32
+ "description": "The prompt slug"
33
+ },
34
+ "textContent": {
35
+ "type": "string",
36
+ "description": "The full text content for the override"
37
+ },
38
+ "model": {
39
+ "type": "string",
40
+ "description": "Optional model override"
41
+ },
42
+ "commitMessage": {
43
+ "type": "string",
44
+ "description": "Optional commit message describing the change"
45
+ }
46
+ },
47
+ "required": [
48
+ "slug",
49
+ "textContent"
50
+ ],
51
+ "additionalProperties": false,
52
+ "$schema": "http://json-schema.org/draft-07/schema#"
53
+ }
54
+ }
mcps/trigger/tools/deploy.json ADDED
@@ -0,0 +1,45 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "deploy",
3
+ "description": "Deploy a project. Use this tool when you need to deploy a project. This will trigger a deployment for the project. This is a long running operation and including a progress token will allow you to display the progress to the user.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "branch": {
16
+ "type": "string",
17
+ "description": "The branch to get tasks for, only used for preview environments"
18
+ },
19
+ "environment": {
20
+ "type": "string",
21
+ "enum": [
22
+ "staging",
23
+ "prod",
24
+ "preview"
25
+ ],
26
+ "description": "The environment to trigger the task in",
27
+ "default": "prod"
28
+ },
29
+ "skipPromotion": {
30
+ "type": "boolean",
31
+ "description": "Skip promoting the deployment to the current deployment for the environment"
32
+ },
33
+ "skipSyncEnvVars": {
34
+ "type": "boolean",
35
+ "description": "Skip syncing environment variables when using the syncEnvVars extension"
36
+ },
37
+ "skipUpdateCheck": {
38
+ "type": "boolean",
39
+ "description": "Skip checking for @trigger.dev package updates"
40
+ }
41
+ },
42
+ "additionalProperties": false,
43
+ "$schema": "http://json-schema.org/draft-07/schema#"
44
+ }
45
+ }
mcps/trigger/tools/dev_server_status.json ADDED
@@ -0,0 +1,16 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "dev_server_status",
3
+ "description": "Check the status of the dev server and view recent output. Shows whether it is stopped, starting, ready, or has errors, along with recent log lines.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "lines": {
8
+ "type": "integer",
9
+ "default": 50,
10
+ "description": "Number of recent log lines to return. Defaults to 50."
11
+ }
12
+ },
13
+ "additionalProperties": false,
14
+ "$schema": "http://json-schema.org/draft-07/schema#"
15
+ }
16
+ }
mcps/trigger/tools/get_current_worker.json ADDED
@@ -0,0 +1,34 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "get_current_worker",
3
+ "description": "Get the current worker for the project, including version and registered task slugs. Use get_task_schema to get the payload schema for a specific task.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ }
30
+ },
31
+ "additionalProperties": false,
32
+ "$schema": "http://json-schema.org/draft-07/schema#"
33
+ }
34
+ }
mcps/trigger/tools/get_prompt_versions.json ADDED
@@ -0,0 +1,41 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "get_prompt_versions",
3
+ "description": "List all versions for a specific prompt. Shows version number, labels (current, override, latest), source (code or dashboard), model, and content.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ },
30
+ "slug": {
31
+ "type": "string",
32
+ "description": "The prompt slug"
33
+ }
34
+ },
35
+ "required": [
36
+ "slug"
37
+ ],
38
+ "additionalProperties": false,
39
+ "$schema": "http://json-schema.org/draft-07/schema#"
40
+ }
41
+ }
mcps/trigger/tools/get_query_schema.json ADDED
@@ -0,0 +1,41 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "get_query_schema",
3
+ "description": "Get the column schema for a specific TRQL table. Available tables: 'runs' (task execution data), 'metrics' (CPU, memory, custom metrics), 'llm_metrics' (LLM token usage, costs, latency). Returns columns, types, descriptions, and allowed values for the specified table.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ },
30
+ "table": {
31
+ "type": "string",
32
+ "description": "The table name to get the schema for (e.g. 'runs', 'metrics', 'llm_metrics')."
33
+ }
34
+ },
35
+ "required": [
36
+ "table"
37
+ ],
38
+ "additionalProperties": false,
39
+ "$schema": "http://json-schema.org/draft-07/schema#"
40
+ }
41
+ }
mcps/trigger/tools/get_run_details.json ADDED
@@ -0,0 +1,50 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "get_run_details",
3
+ "description": "Get the details and trace of a run. Trace events are paginated — the first call returns run details and the first page of trace lines. Pass the returned cursor to fetch subsequent pages without re-fetching the trace. The run ID starts with run_.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ },
30
+ "runId": {
31
+ "type": "string",
32
+ "description": "The ID of the run to get the details of, starts with run_"
33
+ },
34
+ "maxTraceLines": {
35
+ "type": "integer",
36
+ "description": "The maximum number of trace lines per page. Defaults to 200. Use the `cursor` parameter to fetch subsequent pages.",
37
+ "default": 200
38
+ },
39
+ "cursor": {
40
+ "type": "string",
41
+ "description": "Pagination cursor returned from a previous get_run_details call. Pass this to fetch the next page of trace events."
42
+ }
43
+ },
44
+ "required": [
45
+ "runId"
46
+ ],
47
+ "additionalProperties": false,
48
+ "$schema": "http://json-schema.org/draft-07/schema#"
49
+ }
50
+ }
mcps/trigger/tools/get_span_details.json ADDED
@@ -0,0 +1,46 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "get_span_details",
3
+ "description": "Get detailed information about a specific span within a run trace. Use get_run_details first to see the trace and find span IDs (shown as [spanId] in the trace output). Returns timing, properties/attributes, error info, and for AI spans: model, tokens, cost, and response data.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ },
30
+ "runId": {
31
+ "type": "string",
32
+ "description": "The ID of the run to get the details of, starts with run_"
33
+ },
34
+ "spanId": {
35
+ "type": "string",
36
+ "description": "The span ID to get details for. You can find span IDs in the trace output from get_run_details — they appear as [spanId] before each span message."
37
+ }
38
+ },
39
+ "required": [
40
+ "runId",
41
+ "spanId"
42
+ ],
43
+ "additionalProperties": false,
44
+ "$schema": "http://json-schema.org/draft-07/schema#"
45
+ }
46
+ }
mcps/trigger/tools/get_task_schema.json ADDED
@@ -0,0 +1,41 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "get_task_schema",
3
+ "description": "Get the payload schema for a specific task. Use get_current_worker first to see available task slugs.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ },
30
+ "taskSlug": {
31
+ "type": "string",
32
+ "description": "The task slug/identifier to get the payload schema for. Use get_current_worker to see available tasks."
33
+ }
34
+ },
35
+ "required": [
36
+ "taskSlug"
37
+ ],
38
+ "additionalProperties": false,
39
+ "$schema": "http://json-schema.org/draft-07/schema#"
40
+ }
41
+ }
mcps/trigger/tools/initialize_project.json ADDED
@@ -0,0 +1,31 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "initialize_project",
3
+ "description": "Initialize Trigger.dev in your project. This will create a new project in the organization you select and add Trigger.dev to your project.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "orgParam": {
8
+ "type": "string",
9
+ "description": "The organization to create the project in, can either be the organization slug or the ID. Use the list_orgs tool to get a list of organizations and ask the user to select one."
10
+ },
11
+ "projectRef": {
12
+ "type": "string",
13
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
14
+ },
15
+ "projectName": {
16
+ "type": "string",
17
+ "description": "The name of the project to create. If projectRef is not provided, we will use this name to create a new project in the organization you select."
18
+ },
19
+ "cwd": {
20
+ "type": "string",
21
+ "description": "The current working directory of the project"
22
+ }
23
+ },
24
+ "required": [
25
+ "orgParam",
26
+ "projectName"
27
+ ],
28
+ "additionalProperties": false,
29
+ "$schema": "http://json-schema.org/draft-07/schema#"
30
+ }
31
+ }
mcps/trigger/tools/list_dashboards.json ADDED
@@ -0,0 +1,34 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_dashboards",
3
+ "description": "List available built-in dashboards with their widgets. Each dashboard contains pre-built queries for common metrics like run success rates, costs, LLM usage, and more. Use run_dashboard to execute a dashboard's queries.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "environment": {
16
+ "type": "string",
17
+ "enum": [
18
+ "dev",
19
+ "staging",
20
+ "prod",
21
+ "preview"
22
+ ],
23
+ "description": "The environment to get tasks for",
24
+ "default": "dev"
25
+ },
26
+ "branch": {
27
+ "type": "string",
28
+ "description": "The branch to get tasks for, only used for preview environments"
29
+ }
30
+ },
31
+ "additionalProperties": false,
32
+ "$schema": "http://json-schema.org/draft-07/schema#"
33
+ }
34
+ }
mcps/trigger/tools/list_deploys.json ADDED
@@ -0,0 +1,68 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_deploys",
3
+ "description": "List all deploys for a project. Use this tool when you need to search for a deploy or list all deploys for a project.",
4
+ "inputSchema": {
5
+ "type": "object",
6
+ "properties": {
7
+ "projectRef": {
8
+ "type": "string",
9
+ "description": "The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the project ref if running inside a directory that includes a trigger.config.ts file, or if you pass the --project-ref option to the MCP server."
10
+ },
11
+ "configPath": {
12
+ "type": "string",
13
+ "description": "The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the root dir (like in a monorepo setup). If not provided, we will try to find the config file in the current working directory"
14
+ },
15
+ "branch": {
16
+ "type": "string",
17
+ "description": "The branch to get tasks for, only used for preview environments"
18
+ },
19
+ "environment": {
20
+ "type": "string",
21
+ "enum": [
22
+ "staging",
23
+ "prod",
24
+ "preview"
25
+ ],
26
+ "description": "The environment to trigger the task in",
27
+ "default": "prod"
28
+ },
29
+ "from": {
30
+ "type": "string",
31
+ "description": "The date to start the search from, in ISO 8601 format"
32
+ },
33
+ "to": {
34
+ "type": "string",
35
+ "description": "The date to end the search, in ISO 8601 format"
36
+ },
37
+ "period": {
38
+ "type": "string",
39
+ "description": "The period to search within (e.g. 1d, 7d, 3h, etc.)"
40
+ },
41
+ "status": {
42
+ "type": "string",
43
+ "enum": [
44
+ "PENDING",
45
+ "BUILDING",
46
+ "DEPLOYING",
47
+ "DEPLOYED",
48
+ "FAILED",
49
+ "CANCELED",
50
+ "TIMED_OUT"
51
+ ],
52
+ "description": "Filter deployments that are in this status"
53
+ },
54
+ "cursor": {
55
+ "type": "string",
56
+ "description": "The deployment ID to start the search from, to get the next page"
57
+ },
58
+ "limit": {
59
+ "type": "number",
60
+ "minimum": 1,
61
+ "maximum": 100,
62
+ "description": "The number of deployments to return, defaults to 20 (max 100)"
63
+ }
64
+ },
65
+ "additionalProperties": false,
66
+ "$schema": "http://json-schema.org/draft-07/schema#"
67
+ }
68
+ }
mcps/trigger/tools/list_orgs.json ADDED
@@ -0,0 +1,9 @@
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "list_orgs",
3
+ "description": "List all organizations for the current user. Useful when looking up an org slug or ID.",
4
+ "inputSchema": {
5
+ "$schema": "http://json-schema.org/draft-07/schema#",
6
+ "type": "object",
7
+ "properties": {}
8
+ }
9
+ }