Prompt-tool
by ramcavco.huggingface.ramcav/prompt-tool
- Remote endpoint
- 1 tool
Uptime
Checked · every day
99.1%from 6 days of checks
Up without downtime on 3 of 5 days with data; down 60 minutes in all, the longest 30 minutes on 1 November.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1048 ms, slowest 5% 1298 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 88.2%
- Completed the handshake 29.4%
- Listed its tools 29.4%
1 tool at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 5 Nov (today) | No verdict yet | 0 | – |
| 4 Nov | Down 30 minutes | 7of 1 | 829 ms |
| 3 Nov | No downtime | 1of 1 | 1298 ms |
| 2 Nov | No downtime | 1of 1 | 1083 ms |
| 1 Nov | Down 30 minutes | 7of 1 | 1042 ms |
| 31 Oct | No downtime | 1 | 1047 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse prompt-tool https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"prompt-tool": {
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"prompt-tool": {
"type": "sse",
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"prompt-tool": {
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"prompt-tool": {
"type": "sse",
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "prompt-tool"
type: sse
url: "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"prompt-tool":
type: streamable_http
name: "prompt-tool"
enabled: true
uri: "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add prompt-tool --url https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"prompt-tool": {
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"prompt-tool": {
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"prompt-tool": {
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Prompt-tool (`co.huggingface.ramcav/prompt-tool`)
Its page: https://plug.directory/servers/co.huggingface.ramcav/prompt-tool
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse prompt-tool https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"prompt-tool": {
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"prompt-tool": {
"type": "sse",
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"prompt-tool": {
"type": "sse",
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "prompt-tool"
type: sse
url: "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"prompt-tool": {
"url": "https://ramcav-prompt-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 1
prompt_tool_call_prompt_toolPrompt tool which returns an enhancedprompt for any given task. Currently only available for coding and intended for AI-enhanced IDEs. You can choose between "A" or "B" for model—A is the advanced, using gpt-4.1-mini and B is the basic using gpt-4.1-nano. This endpoint requires a prompt (the prompt given by the user) and the tooling available in the host application, so the mcp server can have that information available when crafting the prompt.
From Hugging Face Spaces. Report a problem