To connect GIFs.so through MCP, use a client that supports remote Streamable HTTP servers and the required OAuth flow. The server endpoint is https://gifs.so/api/mcp.
Client interfaces change, so follow your client’s current remote-server setup rather than copying a configuration intended for a different transport or version.
Prepare the account
Create a GIFs.so account and verify your email. Review the integration guide, which includes the current setup instructions and account-key workflow. Keep credentials out of chat prompts and screenshots.
GIFs.so uses OAuth 2.1 with PKCE for MCP. Protected-resource metadata is available at /.well-known/oauth-protected-resource, and authorization-server metadata at /.well-known/oauth-authorization-server on the GIFs.so origin. Let the client use discovery instead of inventing authorization URLs.
Add the remote server
In the client’s MCP or connector settings, add the HTTPS endpoint and complete the authorization flow it presents. GIF tools require the zts:read scope. A workflow that only searches reactions does not need write access.
After connecting, inspect available tools. The expected read tools include list_categories, list_gifs, get_gif, and get_usage. If discovery succeeds but a call fails, distinguish client compatibility from account verification and authorization problems.
Do not convert the endpoint into a local command unless the client’s supported setup explicitly calls for a bridge. A remote HTTP address is not a command-line executable.
Make a small first request
Ask for a few GIFs matching a clear reaction, such as quiet appreciation. Confirm that the assistant uses a real tool result and returns the source or media link supplied by the service.
An assistant may search successfully without being able to render the returned animation inline. That is a display capability issue, not necessarily a search failure. Choose a supported result format or provide the link.
Diagnose without leaking credentials
For connection failures, record the client version, transport, discovery stage, and status after redacting tokens. Check the published llms.txt for changes. Avoid repeated authorization attempts or tight retry loops when the server reports a rate limit.
Once connected, review safe result handling. Discovery permits searching the catalog; posting a GIF to other people remains a separate action requiring the user’s instruction.