Systra Tools is answering right now. Last checked 8 min ago. It exposes 13 tools. Last commit 28 Oct 2026.
Search and pull 500+ production-ready React + Tailwind sections and elements
Uptime history
62 days of history · worst day 99%
62 days agonow
100.0%
Uptime 24h
91 of 91 checks
13
Tools
read from the server
692 ms
Response time
average over 24h
0
Stars
last commit 28 Oct 2026
What changed 62
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 September 2026. No other catalogue keeps this.
6 Nov
a tool description was rewritten
get_component
28 Oct
3 tool descriptions were rewritten
get_component, get_recipe, list_components
28 Oct
the owner changed
27 Oct
13 tool descriptions were rewritten16 times that day
get_component, get_component_styled, get_post and 10 more
27 Oct
12 tools changed the parameters they ask for
get_component, get_component_styled, get_post and 9 more
18 Oct
2 tool descriptions were rewritten
list_images, search_images
18 Oct
2 tools changed the parameters they ask for
list_images, search_images
1 Oct
2 tool descriptions were rewritten
list_images, search_images
27 Sep
13 tool descriptions were rewritten
get_component, get_component_styled, get_post and 10 more
27 Sep
10 tools changed the parameters they ask for
get_component, get_component_styled, get_post and 7 more
and 3 more, back to 27 September 2026
Systra Tools missed one check this week
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add systra-tools --transport http https://systra.tools/api/mcpSettings → Connectors → Add custom connector, then paste this address
https://systra.tools/api/mcp~/.codex/config.toml
[mcp_servers.systra-tools]
url = "https://systra.tools/api/mcp".cursor/mcp.json
{
"mcpServers": {
"systra-tools": {
"url": "https://systra.tools/api/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"systra-tools": {
"type": "http",
"url": "https://systra.tools/api/mcp"
}
}
}Available tools 13
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
component
get_component
Returns the complete, copy-ready React/TSX source of one component as designed, plus notes on its images and any extra files it needs. Components use Tailwind CSS classes and import react, framer-motion and lucide-react; a few also need gsap or three, which the response names with the install command. Use it once you know the exact name; use get_component_styled instead when the component should take on an extracted brand style. Without a premium key, source comes back for the free components, the first six of every category, which list_components and search_components mark as "free"; other names return a notice on how to get a key.
get_component_styled
Returns one component's source together with the tokens of a brand style, step-by-step instructions for mapping the component's colours, fonts and radii onto that style, and the colour values the component uses today. Use it instead of get_component when the result should match a specific brand. The server does not rewrite the code; you apply the mapping. Same premium rule as get_component.
components
list_components
Lists component names, optionally limited to one category, one line each with the name and the category slug. Use it to browse a category before choosing; use search_components instead when you already have a keyword. Returns names only, no source: fetch the code with get_component. Works without a key; without one, the components whose source is free are marked "free".
search_components
Finds components whose name or category contains the search term (one term, case-insensitive substring match) and returns their names with the category slug. Use it when you know roughly what you need, such as 'pricing', 'marquee', 'testimonial' or 'countdown'; use list_components to see a whole category. Names are English PascalCase, so short English words match best. Follow up with get_component for the source.
images
list_images
Lists images and a few videos from the Systra Tools media library (all AI-generated), each with a permanent URL to use directly as src, plus title, album and format. Filter by album and format, 100 per page. Use it to browse an album; use search_images to find a motif by keyword. Without a premium key only the free images are returned, three per album.
search_images
Finds images in the media library (all AI-generated) whose title, tags, file name or album contain every word of the query, and returns their permanent URLs, 100 per page. Use it for a motif, such as 'red dress', 'laptop desk' or 'misty forest'; use list_images to browse a whole album. Titles and tags are English, album keys German. Without a premium key only the free images are included.
categories
list_categories
Lists every component category of the Systra Tools library with its slug, its title and how many components it holds. Start here when the user names a kind of page part (hero, pricing, footer) instead of a component, then pass the slug to list_components. No parameters, works without a key.
post
get_post
Returns one post template as working instructions: the full HTML file, an export script to render it locally as PNG or video, and the rules on what may be changed. The server renders nothing; you edit and export the file. Use it after list_posts.
posts
list_posts
Lists the Instagram post templates (1080 x 1350) with slug, name, family and whether they need your own imagery. Each template is a single HTML file that can be rebuilt and exported as an image or a video. Pass query to search by name or purpose, for example 'quote' or 'statistic'. Use it to pick a slug for get_post.
recipe
get_recipe
Returns one page recipe: the ordered sections with the purpose of each, a composition file where available, and the full source of every section. Pass style to add brand tokens and adaptation instructions. Without a premium key, sections that are not free are named but their source is held back. The answer is long because it contains several complete components.
recipes
list_recipes
Lists curated page recipes: proven section sequences for complete landing pages (for example SaaS, coaching or a hotel), each with its number of sections and a short purpose. Pass query to search by industry, purpose or section, for example 'hotel' or 'pricing'. Use it when the user wants a whole page rather than one section, then call get_recipe.
style
get_style
Returns every design token of one extracted brand style: colours, font families and sizes, spacing, radii, CSS variables and the generated DESIGN.md (up to 4000 characters). Use it to theme your own code or set up a design system; use get_component_styled when you want one specific component already paired with the style.
styles
list_styles
Lists the brand styles extracted from real websites with the Systra style extractor: slug, site name, primary and accent colour and heading font. Pass query to search by site name, domain, colour or font, for example 'bakery' or 'Inter'. Use it to find a slug for get_style, get_component_styled or get_recipe. Works without a key.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://systra.tools/api/mcp | streamable-http | answering | 252 ms | 8 min ago |
Alternatives to Systra Tools
same job, measured the same wayReactFrame
by ahmetloca
Search ReactFrame's React + Tailwind + Motion components, install free ones and price premium picks.
Hello Retail
by helloretail
Set up and tune ecommerce Search, Recommendations, Pages, Email, Product Agents and Analytics.
ProductNow
by productnow
Connect AI agents to ProductNow's context engine to search, create, review, and act.
Lexington
by lexingtonthemes
Finished Tailwind sections and design systems from every Lexington theme, as Astro, React or HTML.
Ballmac
by vamsiy78
Search, inspect and install Ballmac UI React and Tailwind components, blocks and templates.
R
Redfin MCP Server
by thenextgennexus
Redfin property search and full listing detail as agent tools.
Github Tools
by craft-agent
GitHub tools for coding agents: issues, project boards, pull requests, releases and Actions.
Hyperscale Tenant Tools
by hyperscale0
Hyperscale Product reads and contract operations over MCP.
Systra Tools — questions
Answers built from our own checks of this server.
What can Systra Tools do?
It exposes 13 tools, read directly from the server on our last check. Among them: get_component, get_component_styled, get_post, get_recipe, get_style, list_categories and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Systra Tools mostly used for?
Its tools cluster around component, components and images. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Systra Tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 692 ms. The bar chart above shows every period we have measured.
How do I connect Systra Tools?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Systra Tools need an API key?
No. Systra Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Systra Tools?
It answers our handshake in 692 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Systra Tools open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at systra.tools, which runs on its operator's own terms.