Azure DevOps ACTION
Create Project
Queue creation of a new project. Project creation is asynchronous, so this returns an operation reference rather than the finished project - poll the project list to see it appear. Use when onboarding a new team or product area. Example: name
Payments Platform, visibility private, Agile process. See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Azure DevOps account once, then configure and run Create Project from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "azure_devops-create-project",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
azure_devops: { authProvisionId: "apn_xxxxxxx" },
organization: "Organization",
projectName: "Project Name",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "azure_devops-create-project",
"configured_props": {
"azure_devops": { "authProvisionId": "apn_xxxxxxx" },
"organization": "Organization",
"projectName": "Project Name"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "azure_devops",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "azure_devops-create-project",
arguments: {
organization: "Organization",
projectName: "Project Name",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
organization Organization | string | Name of the organization Required Dynamic |
projectName Project Name | string | Name of the new project (max 64 chars, cannot contain / : \ ~ & % ; @ ' " ? < > | # $ * } { , + = [ ]) Required |
description Description | string | Description of the new project Optional |
visibility Visibility | string | Whether the project is private or public. Public projects require the organization to allow public projects. Defaults to private. Optional |
sourceControlType Source Control Type | string | Version control system used by the project. Defaults to Git. Optional |
processTemplateId Process Template ID | string | GUID of the process template to base the project on. Defaults to the built-in Agile template. Run the List Processes action first to obtain other valid values. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- azure_devops-create-project
- Version
- 0.0.2
- App
- Azure DevOps
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗