How do I use myinstants-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@myinstants-mcp play a vine boom sound effect" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

myinstants-mcp

by austenstone

Overview Schema Source Related Servers Score Discussions Admin

JavaScript

Local

fr fr what is this

an MCP server that connects AI agents to myinstants.com — the internet's largest soundboard. millions of meme sounds, vine booms, fart noises, anime clips, gaming sfx, whatever you need bestie.

your AI agent can now:

🔍 search any sound on myinstants
🔴 smash that button and play it through your speakers
📂 browse categories — memes, games, movies, reactions, tiktok trends
📈 check what's trending — stay current fr fr
⏳ wait or don't — block until sound finishes or let it play in the background

this is not a notification beep. this is the entire internet soundboard. your agent has rizz now.

Related MCP server: Sound Effects MCP

the setup is bussin

npx myinstants-mcp

that's it. that's the setup. no cap.

VS Code / GitHub Copilot

Add to your VS Code MCP config (User or .vscode/mcp.json):

{
  "servers": {
    "myinstants": {
      "command": "npx",
      "args": ["-y", "myinstants-mcp@latest"]
    }
  }
}

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "myinstants": {
      "command": "npx",
      "args": ["-y", "myinstants-mcp@latest"]
    }
  }
}

Cursor

.cursor/mcp.json:

{
  "mcpServers": {
    "myinstants": {
      "command": "npx",
      "args": ["-y", "myinstants-mcp@latest"]
    }
  }
}

TIP

works onmacOS out of the box (uses native afplay) — no extra installs needed. on linux just sudo apt install ffmpeg. that's it bestie.

what can it do tho 🤔

🔧 Tools

Tool	What it does	It's giving
`search_sounds`	search myinstants for sounds	`"bruh"` → 20 results with slugs
`browse_category`	browse by category	`"memes"` `"games"` `"reactions"`
`play_sound`	play a sound (by slug, url, or quick search)	`{ query: "sad trombone" }` plays instantly
`get_sound_details`*	get details about a sound (views, uploader, duration)	requires `MYINSTANTS_DETAILS=true`
`list_devices`*	list available audio output devices	requires `MYINSTANTS_DETAILS=true`

* requires MYINSTANTS_DETAILS=true environment variable

`play_sound` options

Parameter	Type	Default	The tea ☕
`query`	string	—	quick search, plays first result. the goat option.
`slug`	string	—	exact slug from search results
`url`	string	—	direct MP3 URL if you're built different
`wait`	boolean	`false`	`false` = plays in background while agent keeps cooking (default 💨). `true` = blocks until done (for dramatic effect 🎭)

📚 Resources

Resource	The vibe
`myinstants://trending`	what's bussin rn in the US 🔥
`myinstants://categories`	all 14 categories no cap
`myinstants://best`	hall of fame. the GOATs. the legends. 🐐

how it works (for the sigma devs)

agent calls play_sound({ query: "vine boom", wait: false })
  → searches myinstants.com
  → finds the MP3 URL
  → streams it through afplay/ffplay/mpv
  → sound plays through your speakers
  → agent keeps cooking while you hear the boom 🍳

sounds queue up automatically. no overlap. your agent can fire multiple sounds and they play one after another. sheesh.

teach your agent to troll you 💀

drop a .instructions.md in your repo (with applyTo: "**" in the frontmatter) and your agent will play sounds while it works. imagine: vine boom when it finds a bug. sad trombone when your tests fail. rick roll mid-code-review for absolutely no reason.

---
name: "Soundboard"
description: "Sounds for all contexts"
applyTo: "**"
---

Play sounds using the myinstants MCP server while you work:
- Play `play_sound(query: "vine boom sound")` when you find cursed code
- Play `play_sound(query: "sad trombone")` when the user's code doesn't work
- Play `play_sound(query: "minecraft level up sound")` when you fix something

check our myinstants.instructions.md for the full unhinged setup. your agent will never be an NPC again. 🏆

config

env vars

Variable	Default	The tea ☕
`MYINSTANTS_VOLUME`	`0.5`	how loud (0-1). crank it bestie.
`MYINSTANTS_WAIT`	`false`	`"true"` = sounds block until finished. dramatic effect mode 🎭
`MYINSTANTS_DEVICE`	(system default)	route audio to a specific output device. platform-specific device name.
`MYINSTANTS_PLAYER`	(auto)	force a specific player: `ffplay`, `mpv`, `afplay`, or `paplay`.
`MYINSTANTS_DETAILS`	`false`	`"true"` = enables `get_sound_details` and `list_devices` tools.

{
  "servers": {
    "myinstants": {
      "command": "npx",
      "args": ["-y", "myinstants-mcp@latest"],
      "env": {
        "MYINSTANTS_VOLUME": "0.8",
        "MYINSTANTS_DEVICE": "Denon AVR-S760H",
        "MYINSTANTS_DETAILS": "true"
      }
    }
  }
}

audio device selection

route sounds to a specific output device instead of system default:

# set device name (platform-specific)
export MYINSTANTS_DEVICE="Denon AVR-S760H"

# force a specific player (optional)
export MYINSTANTS_PLAYER="ffplay"

# enable device listing tool
export MYINSTANTS_DETAILS="true"

discover available devices:

# macOS
ffmpeg -f avfoundation -list_devices true -i "" 2>&1

# Linux (PulseAudio)
pactl list short sinks

# mpv (cross-platform)
mpv --audio-device=help

or use the list_devices tool when MYINSTANTS_DETAILS=true — your agent can discover devices for you. 💅

player support:

Player	Device Flag	Example
`ffplay`	`-audio_device`	`ffplay -audio_device "Denon AVR-S760H"`
`mpv`	`--audio-device=`	`mpv --audio-device="pulse/alsa_output.usb"`
`paplay`	`--device=`	`paplay --device=bluez_sink.XX`
`afplay`	❌ N/A	macOS system default only (no device selection)

notes:

default behavior unchanged — uses system default output if MYINSTANTS_DEVICE not set
afplay on macOS doesn't support device selection — set MYINSTANTS_PLAYER=ffplay or mpv if you need device control
device names are platform-specific (see discovery commands above)
Windows PowerShell player doesn't support device selection — install ffmpeg or mpv for device support

audio player support

Player	Platform	Install	Vibe
`afplay`	macOS	pre-installed 💅	just works. zero effort. slay.
`ffplay`	everywhere	`brew install ffmpeg` / `apt install ffmpeg`	the reliable bestie
`mpv`	everywhere	`brew install mpv` / `apt install mpv`	also valid no cap

auto-detects what you have. tries afplay first on mac, then ffplay, then mpv. fallback chain is bussin.

why tho 💀

because your AI agent should be able to hit you with a vine boom when the code compiles. because sad trombone when tests fail is objectively correct. because the bruh button exists and your agent deserves to press it. this is not delulu — this is the future.

every other MCP sound server plays one notification beep. one beep. that's giving NPC energy. we have millions of sounds. the entire internet soundboard. main character behavior only.

it's giving... open source 💅

made by @austenstone 🏷️

no cap this might be the most unhinged MCP server ever and we're lowkey proud of it 💀🔥

Available Tools

3 tools

browse_categoryC

Browse sounds by category on myinstants.com.

ParametersJSON Schema

Name	Required	Description	Default
`category`	Yes	Category name: anime & manga, games, memes, movies, music, politics, pranks, reactions, sound effects, sports, television, tiktok trends, viral, whatsapp audios

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but lacks details on permissions, rate limits, pagination, or what the output looks like (e.g., list of sounds with metadata). This is a significant gap for a tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It is front-loaded with the core purpose, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., sound listings, links, metadata) or behavioral aspects like error handling. For a tool with such minimal structured data, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'category' fully documented in the schema (including allowed values). The description adds no additional meaning beyond implying category-based browsing, so it meets the baseline of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('browse') and resource ('sounds by category') with the specific domain 'myinstants.com'. It distinguishes from 'play_sound' (which plays rather than browses) and 'search_sounds' (which searches rather than browses by category), though it doesn't explicitly mention these distinctions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'search_sounds' is provided. The description implies usage for category-based browsing but doesn't specify scenarios or exclusions, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

play_soundA

Play a sound from myinstants.com. Returns the sound duration in seconds so you can plan around async playback.

ParametersJSON Schema

Name	Required	Description
`slug`	No	Sound slug from search results
`url`	No	Direct MP3 URL
`query`	No	Quick search — plays first result
`wait`	No	Wait for sound to finish before returning (default: false). Set true only for dramatic moments where timing matters.

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by explaining the return behavior ('Returns the sound duration in seconds') and async nature ('plan around async playback'), but it lacks details on potential errors, rate limits, or authentication needs. It provides useful context but not comprehensive behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded, consisting of just two sentences that efficiently convey the tool's purpose and key behavioral detail. Every word earns its place, with no wasted text, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is reasonably complete. It covers the purpose, return value, and async behavior, but it could improve by mentioning error handling or usage constraints. Without an output schema, it does explain the return type, which helps compensate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description does not add any parameter-specific semantics beyond what the schema provides, such as explaining the relationships between slug, url, and query. It meets the baseline for high schema coverage but does not enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Play a sound from myinstants.com') and resource ('sound'), distinguishing it from sibling tools like browse_category and search_sounds which are for discovery rather than playback. It also specifies the return value ('Returns the sound duration in seconds'), making the purpose explicit and distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for usage ('so you can plan around async playback') and implies when to use it (for playing sounds rather than browsing or searching). However, it does not explicitly state when not to use it or name alternatives among the sibling tools, which prevents a perfect score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_soundsC

Search myinstants.com for sound buttons.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Search query

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't describe what the search returns (sound files, metadata, links), whether results are paginated, rate limits, authentication requirements, or error conditions. 'Search' implies read-only behavior, but this isn't explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single sentence with zero wasted words. It's front-loaded with the core functionality and uses straightforward language. Every word earns its place in communicating the essential purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what kind of results to expect (sound files, metadata, URLs), how results are structured, or any behavioral aspects like pagination or error handling. The agent would be operating with significant uncertainty about the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100% with the single 'query' parameter well-documented, so the description doesn't need to compensate. The description adds no additional parameter semantics beyond what's in the schema, which is acceptable given the comprehensive schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Search') and target resource ('myinstants.com for sound buttons'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'browse_category' or 'play_sound' - a search tool could potentially overlap with browsing functionality without clearer boundaries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance about when to use this tool versus alternatives like 'browse_category' or 'play_sound'. There's no mention of prerequisites, appropriate contexts, or limitations that would help an agent choose between these related sound-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.8.2Mar 21, 2026
- First observedbrowse_category
- First observedplay_sound
- First observedsearch_sounds

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: browse_category is for exploring sounds by category, search_sounds is for keyword-based searching, and play_sound is for playing a specific sound. There is no overlap in functionality, making it easy for an agent to select the right tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case: browse_category, play_sound, and search_sounds. This predictability enhances usability and reduces confusion.

Tool Count5/5

With 3 tools, the server is well-scoped for its purpose of interacting with myinstants.com. Each tool serves a distinct and essential function, avoiding bloat while covering key operations for sound discovery and playback.

Completeness5/5

The tool set provides complete coverage for the domain: browse_category and search_sounds enable sound discovery, and play_sound handles playback. There are no obvious gaps, as these tools support the core workflows of finding and playing sounds from the website.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

sounds A
com.sfxmint
Free CC0 sound effects for agents: ask by role (button-click, coin), sets, or search 4,600+.
Audio Processing Multimedia Processing
61
OriginGrid A
net.origingrid
AI Agent Source Registry. 288K+ curated sources for agentic search and discovery.
Search Agent Orchestration
191
agent-media-toolkit B
io.github.krakonjac300-pixel
15 media & data tools for AI agents: search, transcribe, subtitles, voiceover, translate & more.
Multimedia Processing Audio Processing Language Translation
1521
CrackedOAuth
io.github.systemsailab
Discover, inspect and run 63,000+ agent tools from one balance. Pay per call, no subscriptions.
Autonomous Agents
1

Related MCP Servers

MCP Play Sound Server
Audio Processing Developer Tools
davidteren
A
license
Not graded
quality
F
maintenance
Provides audio playback functionality for AI agents, allowing them to play notification sounds when coding tasks are completed.
Updated a year ago (2025-06-04 18:35 UTC)
1
MIT
Sound Effects MCP
Multimedia Processing Audio Processing App Automation
sawa-zen
A
license
B
quality
D
maintenance
Plays sound effects (completion, newtype, and error sounds) in response to various situations like task completion, insights, or errors. Integrates with Claude Desktop to provide audio feedback for improved workflow efficiency and entertainment.
Updated a year ago (2025-07-29 16:14 UTC)
2
12
6
MIT
Freesound MCP
Audio Processing Search Multimedia Processing
MuShan-bit
A
license
B
quality
D
maintenance
Enables searching and downloading audio samples from Freesound using keywords, filters, and sound IDs. It provides detailed sound metadata including duration, license information, and preview URLs.
Updated 7 months ago (2026-01-30 12:49 UTC)
2
20
1
MIT
social-intel-mcp
Social Media Research & Data
FoundryNet
A
license
Not graded
quality
F
maintenance
Provides AI agents with real-time social trends, cross-platform sentiment, viral content velocity, and brand mentions from Reddit, Hacker News, and Google Trends.
Updated a month ago (2026-08-11 06:21 UTC)
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/austenstone/myinstants-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

fr fr what is this

the setup is bussin

VS Code / GitHub Copilot

Claude Desktop

Cursor

what can it do tho 🤔

🔧 Tools

play_sound options

📚 Resources

Categories

how it works (for the sigma devs)

teach your agent to troll you 💀

config

env vars

audio device selection

audio player support

why tho 💀

it's giving... open source 💅

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

`play_sound` options