Skip to content

updated inspector usage #195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 30, 2025
Merged

updated inspector usage #195

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 14 additions & 5 deletions docs/developer_guide/DEVELOPER_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -340,16 +340,25 @@ This split keeps MCP concerns (transport, context, auth, formatting) in the serv

## Interactive testing using the MCP Inspector

The MCP inspector provides you with a convenient way to browse and test tools, resources and prompts:
The [MCP inspector](https://www.npmjs.com/package/@modelcontextprotocol/inspector/v/0.9.0) provides you with a convenient way to browse and test tools, resources and prompts:

**For development environment:**
You can use the inspector to directly run the MCP server and connect over stdio:

**Using the development environment:**
```bash
uv run mcp dev ./src/teradata_mcp_server/server.py
npx modelcontextprotocol/inspector uv run teradata-mcp-server
```

**Using the installed package:**
```bash
npx modelcontextprotocol/inspector teradata-mcp-server
```

**For installed package:**
You may also run the MCP server as a separate process and connect to it form the inspector over http:

```bash
mcp dev teradata-mcp-server
uv run teradata-mcp-server --mcp_transport streamable-http
npx modelcontextprotocol/inspector
```

## Build, Test, and Publish
Expand Down