Skip to content

Commit 09d3ed8

Browse files
committed
mcp_server.md edited online with Bitbucket
1 parent 7181d0c commit 09d3ed8

1 file changed

Lines changed: 22 additions & 0 deletions

File tree

netapp_dataops_traditional/docs/mcp_server.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,8 @@ After installation, the netapp_dataops_ontap_mcp.py command will be available in
4343

4444
#### Usage
4545

46+
##### DataOps Toolkit Config File
47+
4648
A config file must be created before the NetApp Data Management Toolkit for Traditional Environments can be used to perform data management operations. For more details [click here](https://github.com/NetApp/netapp-dataops-toolkit/tree/main/netapp_dataops_traditional#getting-started).
4749

4850
If you do not have a config file, you can run the following command to create one.
@@ -51,6 +53,26 @@ If you do not have a config file, you can run the following command to create on
5153
uvx --from netapp-dataops-traditional netapp_dataops_cli.py config
5254
```
5355

56+
##### Example JSON Config
57+
58+
To use the MCP server with an MCP client, you need to configure the client to use the server. For many clients (such as [VS Code](https://code.visualstudio.com/docs/copilot/chat/mcp-servers), [Claude Desktop](https://modelcontextprotocol.io/quickstart/user), and [AnythingLLM](https://docs.anythingllm.com/mcp-compatibility/overview)), this requires editing a config file that is in JSON format. Below is an example. Refer to the documentation for your MCP client for specific formatting details.
59+
60+
```json
61+
{
62+
"mcpServers": {
63+
"netapp_dataops_ontap_mcp": {
64+
"type": "stdio",
65+
"command": "uvx",
66+
"args": [
67+
"--from",
68+
"/home/ailab/git/bitbucket/netapp-dataops-toolkit/netapp_dataops_traditional",
69+
"netapp_dataops_ontap_mcp.py"
70+
]
71+
}
72+
}
73+
}
74+
```
75+
5476
### Support
5577

5678
Report any issues via GitHub: https://github.com/NetApp/netapp-dataops-toolkit/issues.

0 commit comments

Comments
 (0)