MCP Servers That Connect AI to Your Tools Safely

Who it helps

Business owners who want AI to work with the tools they already use, like a website, a photo library or search reports, with access limited to the job. An MCP server is the connection that lets AI use an outside tool. The useful work is deciding what AI is allowed to do through that connection, and making the risky actions unavailable.

Frog Stone Media builds, audits or forks these connections depending on the job. Some are written from scratch. Some are open-source servers that get reviewed and patched before they are trusted with an account.

What the connections do

Stock photos with credit built in

The stock photo server lets AI search licensed photo and video libraries while it works on an article or a page. When one photo service is slow or down, the search still returns results from the others and says which source had trouble, so the work keeps moving. Every result carries a ready-to-paste photographer credit, which the photo library’s terms require.

Saving files is the one action that writes anything, so it is locked down. It only downloads from the photo services’ own servers, only saves images and video, and only saves into one folder that someone chose on purpose. Saving stays switched off until someone chooses that folder.

WordPress that waits for a person

The WordPress connection lets AI read posts, create drafts, update posts and upload images on a live WordPress site. New posts default to drafts, and publishing and edits to live posts are left to a person to approve in the workflow. It also refuses to change an article’s original publish date, so an older article keeps its place in search results and in the feed.

The connection strips publication dates and saves new posts as drafts by default.

Search reports from an audited open-source server

Search Console and Bing reporting runs through an open-source server rather than a new one. Before it got access to any site, Michael reviewed its code for security and correctness and patched what needed fixing. It now pulls Google and Bing search data for SEO reporting: which searches bring visitors, which pages are close to ranking higher, and where traffic has dropped. When a good tool already exists, auditing and hardening it is often the better choice than writing a new one.

Amazon product lookups

A separate server gives AI product details for affiliate links, so product information comes straight from Amazon. It has its own page: Amazon Creators API.

What it does for the business

• Smoother operations. AI finds photos, drafts posts and pulls search reports inside the tools already in use.
• Revenue growth. Search reports point to pages worth improving, and product lookups keep affiliate links tied to real product data.
• Happier customers. New posts start as drafts and a person approves publishing, so readers see finished work.

How the work gets checked

Claude Code builds. OpenAI Codex reviews. Human verified and approved. A person reviews the work and how it fits your business before it goes live. These connections are one part of the larger setup described in How Frog Stone Media Runs Its Own Businesses on AI. To connect AI to your own tools, see MCP development.

For your technical team

• Stock images: a TypeScript MCP server that replaces a third-party Pexels server at feature parity and adds Pixabay. Search runs as a waterfall: Pexels first, Pixabay only when Pexels underfills. Responses carry results, the sources that succeeded and warnings, so a single provider failure degrades to a warning.
• Download tool: HTTPS only, allowlisted Pexels and Pixabay CDN hosts revalidated on every redirect, image or video content types only, a size cap, and writes confined to one configured directory with no traversal, absolute paths or symlink escape. Enabled only when that directory is configured.
• WordPress bridge: wraps the REST API for get, list, create draft, update, media upload, featured-image upload and registered abilities. Publish dates are stripped from every create and update payload in the request layer, and new posts default to draft unless a status is passed. Customizer and theme tools moved to a companion WordPress plugin that serves them as typed tools.
• Search Console and Bing server: a fork of an open-source MCP server, reviewed and patched for security and correctness before it was connected to any property.
• Credentials load from project-local environment files and stay out of committed configuration.
• Testing: Vitest unit tests over the merge and attribution logic, and characterization tests against recorded WordPress API responses.