You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can use Port's MCP to find the use cases that will be valuable to you. Try using this prompt: "think of creative prompts I can use to showcase the power of Port's MCP, based on the data available in Port"
118
119
119
-
120
-
## Installing Port MCP
121
-
122
-
Installing Port's MCP is simple. Follow the instructions for your preferred tool, or learn about the archived local MCP server.
123
-
124
-
<TabsgroupId="mcp-setup"queryString>
125
-
<TabItemvalue="cursor"label="Cursor">
126
-
To connect Cursor to Port's remote MCP, follow these steps:
127
-
128
-
1.**Go to Cursor settings, click on Tools & Integrations, and add a new MCP server**
129
-
130
-
131
-
132
-
2.**Add the above configuration**
133
-
134
-
Use the appropriate configuration for your region:
In some cases, after clicking "Accept" in the authentication popup, the window won't get closed but the connection is established successfully. You can safely close the window.
173
-
174
-
If you still don't see the tool, try it a couple of times. We are aware of this behavior and working to improve it.
175
-
:::
176
-
177
-
</TabItem>
178
-
<TabItemvalue="vscode"label="VSCode">
179
-
To connect VSCode to Port's remote MCP server, follow these detailed steps. For complete instructions, refer to the [official VS Code MCP documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers).
180
-
181
-
:::info VSCode MCP requirements
182
-
Before proceeding, ensure your VS Code is updated to the latest version and that MCP is enabled for your GitHub organization. You may need to enable "Editor preview features" under Settings > Code, planning, and automation > Copilot via admin access from your organization.
183
-
:::
184
-
185
-
:::tip Prerequisites
186
-
This configuration uses the open-source `mcp-remote` package, which requires Node.js to be installed on your system. Before using the configuration, ensure Node.js is available by running:
187
-
188
-
```bash
189
-
npx -y mcp-remote --help
190
-
```
191
-
192
-
If you encounter errors:
193
-
-**Missing Node.js**: Install Node.js from [nodejs.org](https://nodejs.org/)
194
-
-**Network issues**: Check your internet connection and proxy settings
195
-
-**Permission issues**: You may need to run with appropriate permissions
196
-
:::
197
-
198
-
:::warning VSCode action tool issue
199
-
In some versions of VS Code, the MCP server might not start or return an error in the chat because of a configuration issue with the action related tools. To deal with it, [deselect](./available-tools#select-which-tools-to-use) the tools `create_action`, `update_action`, and `delete_action`.
200
-
This is relevant for cases where you see an error like this one:
201
-
```
202
-
Failed to validate tool mcp_port_create_action: Error: tool parameters array type must have items. Please open a Github issue for the MCP server or extension which provides this tool
203
-
```
204
-
:::
205
-
206
-
**Step 1: Configure MCP Server Settings**
207
-
208
-
1. Open VS Code settings
209
-
2. Search for "MCP: Open user configuration" (or follow the instructions on a workspace installation)
210
-
3. Add the server configuration using the appropriate configuration for your region:
211
-
212
-
<Tabs>
213
-
<TabItemvalue="eu"label="EU">
214
-
```json showLineNumbers
215
-
{
216
-
"mcpServers": {
217
-
"port-vscode-eu": {
218
-
"command": "npx",
219
-
"args": [
220
-
"-y",
221
-
"mcp-remote",
222
-
"https://mcp.port.io/v1"
223
-
]
224
-
}
225
-
}
226
-
}
227
-
```
228
-
</TabItem>
229
-
<TabItemvalue="us"label="US">
230
-
```json showLineNumbers
231
-
{
232
-
"mcpServers": {
233
-
"port-vscode-us": {
234
-
"command": "npx",
235
-
"args": [
236
-
"-y",
237
-
"mcp-remote",
238
-
"https://mcp.us.port.io/v1"
239
-
]
240
-
}
241
-
}
242
-
}
243
-
```
244
-
</TabItem>
245
-
</Tabs>
246
-
247
-
**Step 2: Start the MCP Server**
248
-
249
-
1. After adding the configuration, click on "Start" to initialize the MCP server
250
-
2. If you don't see the "Start" button, ensure:
251
-
- Your VS Code version is updated to the latest version
252
-
- MCP is enabled for your GitHub organization
253
-
- "Editor preview features" is enabled under Settings > Code, planning, and automation > Copilot
254
-
255
-
**Step 3: Verify Connection**
256
-
257
-
1. Once started, you should see the number of available tools displayed
258
-
2. If you don't see the tools count:
259
-
- Click on "More" to expand additional options
260
-
- Select "Show output" to view detailed logs
261
-
- Check the output panel for any error messages or connection issues
262
-
263
-
**Step 4: Access Port Tools**
264
-
265
-
1. Start a new chat session in VS Code
266
-
2. Click on the tools icon in the chat interface
267
-
3. You should now see Port tools available for use
To connect Claude to Port's remote MCP, you need to create a custom connector. This process does not require a client ID. For detailed instructions, refer to the [official Anthropic documentation on custom connectors](https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp).
274
-
275
-
When prompted for the remote MCP server URL, use the appropriate URL for your region:
276
-
277
-
<Tabs>
278
-
<TabItemvalue="eu"label="EU">
279
-
```
280
-
https://mcp.port.io/v1
281
-
```
282
-
</TabItem>
283
-
<TabItemvalue="us"label="US">
284
-
```
285
-
https://mcp.us.port.io/v1
286
-
```
287
-
</TabItem>
288
-
</Tabs>
289
-
</TabItem>
290
-
<TabItemvalue="local-mcp"label="Local MCP">
291
-
The local MCP server is an open-source project that you can run on your own infrastructure. It offers a similar set of capabilities, but requires manual setup and maintenance.
292
-
293
-
While you can use it, we are no longer supporting it and are not tracking the project issues and activities.
294
-
295
-
<h2>Prerequisites</h2>
296
-
297
-
- A Port.io account with appropriate permissions.
298
-
- Your Port credentials (Client ID and Client Secret). You can create these from your Port.io dashboard under Settings > Credentials.
299
-
300
-
<h2>Installation</h2>
301
-
302
-
The Port MCP Server can be installed using Docker or `uvx` (a package manager for Python). While the setup is straightforward, the specifics can vary based on your chosen MCP client (Claude, Cursor, VS Code, etc.).
303
-
304
-
:::info Detailed Installation Guide
305
-
For comprehensive, step-by-step installation instructions for various platforms and methods (Docker, UVX), please refer to the **[Port MCP Server GitHub README](https://github.com/port-labs/port-mcp-server)**.
306
-
The README provides the latest configuration details and examples for different setups.
Copy file name to clipboardExpand all lines: docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/azure/resource_templates/advanced.md
+78-6Lines changed: 78 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,13 +18,25 @@ import WebAppBlueprint from './compute_resources/\_web_app_blueprint.mdx'
18
18
import DatabaseAppConfig from './database_resources/\_port_app_config.mdx'
19
19
import PostgresFlexibleServerBlueprint from './database_resources/\_postgres_flexible_server_blueprint.mdx'
20
20
21
+
import ServiceBusNamespaceBlueprint from './service_bus/\_service_bus_namespace_blueprint.mdx'
22
+
import ServiceBusQueueBlueprint from './service_bus/\_service_bus_queue_blueprint.mdx'
23
+
import ServiceBusTopicBlueprint from './service_bus/\_service_bus_topic_blueprint.mdx'
24
+
import ServiceBusSubscriptionBlueprint from './service_bus/\_service_bus_subscription_blueprint.mdx'
25
+
import ServiceBusAppConfig from './service_bus/\_port_app_config.mdx'
21
26
22
-
## Mapping Storage Resources
27
+
import ApplicationInsightsBlueprint from './application_insights/\_blueprint.mdx'
28
+
import ApplicationInsightsAppConfig from './application_insights/\_port_app_config.mdx'
29
+
30
+
import KeyVaultBlueprint from './key_vault/\_blueprint.mdx'
31
+
import KeyVaultAppConfig from './key_vault/\_port_app_config.mdx'
32
+
33
+
34
+
## Mapping storage resources
23
35
24
36
The following example demonstrates how to ingest your Azure Storage Accounts and Containers to Port.
25
37
You can use the following Port blueprint definitions and integration configuration:
26
38
27
-
:::note
39
+
:::note Resource group requirement
28
40
The Storage Account has a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
29
41
:::
30
42
@@ -39,12 +51,12 @@ Here are the API references we used to create those blueprints and app config:
The following example demonstrates how to ingest your Azure Database Resources to Port.
74
86
You can use the following Port blueprint definitions and integration configuration:
75
87
76
-
:::note
88
+
:::note Resource group requirement
77
89
The Database Resources below have a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
78
90
:::
79
91
@@ -85,6 +97,66 @@ Here are the API references we used to create those blueprints and app config:
The following example demonstrates how to ingest your Azure Service Bus resources (Namespaces, Queues, Topics, and Subscriptions) to Port.
103
+
You can use the following Port blueprint definitions and integration configuration:
104
+
105
+
:::note Hierarchical relationships
106
+
The Service Bus resources have a hierarchical relationship. The Namespace relates to the Resource Group, Queues and Topics relate to the Namespace, and Subscriptions relate to Topics. Creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
107
+
:::
108
+
109
+
<ServiceBusNamespaceBlueprint/>
110
+
111
+
<ServiceBusQueueBlueprint/>
112
+
113
+
<ServiceBusTopicBlueprint/>
114
+
115
+
<ServiceBusSubscriptionBlueprint/>
116
+
117
+
<ServiceBusAppConfig/>
118
+
119
+
Here are the API references we used to create those blueprints and app config:
120
+
121
+
-[Service Bus Namespace](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/namespaces/list-by-subscription)
122
+
-[Service Bus Queue](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/queues/list-by-namespace)
123
+
-[Service Bus Topic](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/topics/list-by-namespace)
124
+
-[Service Bus Subscription](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/subscriptions/list-by-topic)
125
+
126
+
## Mapping application insights
127
+
128
+
The following example demonstrates how to ingest your Azure Application Insights components to Port.
129
+
You can use the following Port blueprint definitions and integration configuration:
130
+
131
+
:::note Resource group requirement
132
+
Application Insights has a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
133
+
:::
134
+
135
+
<ApplicationInsightsBlueprint/>
136
+
137
+
<ApplicationInsightsAppConfig/>
138
+
139
+
Here are the API references we used to create those blueprints and app config:
The resources in this page are only few of the resources that the Azure Exporter supports.
90
162
If you don't find the Azure resource you want to map to Port head to the [Mapping Extra Resources](/build-your-software-catalog/sync-data-to-catalog/cloud-providers/azure/resource_templates/mapping_extra_resources.md) page to learn about what kind of azure resources are supported by the Azure integration and how to map them into Port.
0 commit comments