No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi...is anyone using github copilot agent with building pulumi components?

I tested it. Any specific issues? you might like pulumi mcp :

<https://www.pulumi.com/docs/iac/guides/ai-integration/mcp-server/>

No...i just have been having really good success from it and can mostly open a github issue and assign it to the agent to go and do on its own and come back with a PR.  Just wondering if other has been using it and if they have their tips and tricks.

Ive seen this mcp server but it requires oauth which for some weird reason github agent doesnt support yet.  Any hints or work around for that?

```The Pulumi MCP server is hosted at <https://mcp.ai.pulumi.com/mcp> and uses OAuth authentication. When you first connect, a web page will open where you'll enter your Pulumi Access Token and select which organization to use.```
Any thoughts on how i can setup the github agent to use this?

We did have a local pulumi mcp I wonder if its still available

See if something like this works:

```{
  "mcpServers": {
    "pulumi": {
      "command": "npx",
      "args": [
        "@Pulumi Team/mcp-server@latest",
        "stdio"
      ],
      "transportType": "stdio"
      // optionally add environment variables, working directory, etc.
    }
  }
}```

Thanks.  Looks like github has a little different usage.  I messed around with it and it took this:
```        {
          "mcpServers": {
            "pulumi": {
              "type": "local",
              "command": "npx",
              "args": [ "@pulumi/mcp-server@latest", "stdio" ],
              "tools": ["*"]
            }
          }
        }```

Looks like it is starting...

```args: @pulumi/mcp-server@latest stdio 
cwd: /home/runner/work/infrastructure/infrastructure
Starting MCP client for pulumi with command: npx and args: @pulumi/mcp-server@latest stdio
Creating MCP client for pulumi...
Connecting MCP client for pulumi...
...
...
MCP client for pulumi connected, took 27416ms
Started MCP client for pulumi
...
...
Fetching tools from client: pulumi
Tool pulumi-registry-get-type added to tools list for client: pulumi
Tool pulumi-registry-get-resource added to tools list for client: pulumi
Tool pulumi-registry-get-function added to tools list for client: pulumi
Tool pulumi-registry-list-resources added to tools list for client: pulumi
Tool pulumi-registry-list-functions added to tools list for client: pulumi
Tool pulumi-cli-preview added to tools list for client: pulumi
Tool pulumi-cli-up added to tools list for client: pulumi
Tool pulumi-cli-stack-output added to tools list for client: pulumi
Tool pulumi-cli-refresh added to tools list for client: pulumi
Tool deploy-to-aws added to tools list for client: pulumi
Tool pulumi-resource-search added to tools list for client: pulumi
Tool neo-task-launcher added to tools list for client: pulumi
Successfully retrieved 12 tools from client: pulumi
Updated session log for pulumi with 12 tools```