Postman AI

Postman AI AI

Postman AI AI

Postman AI AI

Postman AI AI

Postman AI AI

Postman AI AI

Postman AI AI

Postman AI AI

Postman AI AI

Postman AI AI

I built a free, open source app that lets you remotely control codex and other AI agents

lunel is a free and open source app that lets you code from your phone with real dev tools and ai agents like Codex, Claude Code, and OpenCode You get: - ai agents - code editor with file explorer - built-in browser with devtools - real terminal - git support - api client (like postman) - ports manager (view & kill ports) - process manager (control running tasks) - activity monitor (cpu, memory, network) - even brainrot (auto switch to Instagram / YouTube while ai runs) its fully open source, end to end encrypted, no signup, and supports both ios + android Github repo: https://github.com/lunel-dev/lunel Website: https://lunel.dev IOS App: https://apps.apple.com/us/app/lunel/id6759504065 Android APK: https://github.com/lunel-dev/lunel/releases/download/v0/lunel-v2.apk submitted by /u/rinkitadhana [link] [comments]

I got mass of MCP servers from OpenAPI / Postman / GraphQL specs using ~3 commands

I've been wiring up MCP servers for different APIs at work and got tired of the manual grind. Every API has a slightly different spec format — some are OpenAPI 3.x, some are old Swagger 2.0, some teams only have Postman collections, and one team somehow only had GraphQL SDL files. So I built a CLI that handles all of them. You point it at a spec file and it spits out typed MCP tool definitions, full TypeScript or Python server scaffolds, or function-calling schemas for OpenAI/Anthropic. Here's what the flow looks like: ```bash Inspect what's in the spec ruah conv inspect stripe-openapi.yaml Generate a full MCP TypeScript server ruah conv generate stripe-openapi.yaml --target mcp-ts-server Or just get tool definitions for Claude ruah conv generate stripe-openapi.yaml --target anthropic ``` The part I'm actually proud of is the risk classification. Every generated tool gets tagged as safe, moderate, or destructive based on the HTTP method, the endpoint pattern, and whether it mutates state. So when you hand 47 tools to an agent, you can immediately see which ones need human approval. Example output: → 47 tools generated from stripe-openapi.yaml → Risk breakdown: 31 safe, 12 moderate, 4 destructive → Destructive: delete_customer, cancel_subscription, refund_charge, void_invoice It also handles auth normalization (API keys, OAuth, Bearer tokens all get wrapped consistently), pagination/retry wrappers, and dry-run mode so you can test without hitting the actual API. Supports these input formats: - OpenAPI 3.x / Swagger 2.0 - Postman Collection v2.1 - GraphQL SDL - HAR files (recorded browser traffic) And these output targets: - MCP server (TypeScript or Python scaffold) - MCP tool definitions (JSON) - OpenAI function-calling schema - Anthropic tool schema - A2A service wrappers It's open source (MIT), zero config, single runtime dependency (yaml). Curious if anyone else has been dealing with this. What's your current workflow for getting APIs into your agent toolchains? submitted by /u/ImKarmaT [link] [comments]

Restk — First API client built for today's developer workflow. Claude Code can manage your APIs without seeing your secrets.

Claude talks to Restk via MCP If you're using Claude Code for development, you've probably hit this wall: you want Claude to help with API work — debug a failing endpoint, generate tests, import an OpenAPI spec — but your API workspace is full of secrets. Auth tokens, API keys, production credentials, PII in response bodies. You can't just hand all that to an AI. Restk is the first API client that's deeply integrated with Claude Code. One command and Claude can work with your entire API workspace — while your secrets stay on your machine. How it works: Claude talks to Restk via MCP Claude Code doesn't touch your APIs directly. It communicates with Restk through MCP (Model Context Protocol). Claude sends instructions → Restk executes them → Restk returns sanitized results back to Claude. Your real data never leaves Restk. All responses that flow back to Claude go through Restk's schema extraction engine — real values are stripped and replaced with synthetic data that matches the original types: Your API returns: {"email": "john@company.com", "api_key": "sk-live-abc123"} Restk sends Claude: {"email": "synthetic_7f@example.com", "api_key": "[REDACTED]"} Auth headers — Authorization, Cookie, X-API-Key — always redacted. Claude reasons about structure and types, never about your actual data. This happens automatically on every response, every tool call. No configuration needed. What can Claude do through Restk? Here are real examples from my daily workflow: Browse your workspace: "Show me all the requests in the Payments collection" — Claude asks Restk to list requests. Restk returns names, methods, URLs, and IDs. Claude can then get details for any specific request — URL, headers, parameters, body, auth type — with all sensitive values sanitized. Send requests and debug failures: "Send the Create User request" — Claude tells Restk which request to run. Restk executes it using the currently active environment and returns the sanitized response — status code, headers, body schema with synthetic values, timing. If it fails? Claude can pull the request details and response history (all sanitized) to diagnose the issue. No more copy-pasting between tools. Write tests: "Generate a test script for the Login endpoint" — Claude asks Restk to generate a Nova test script for a specific request. Restk creates JavaScript tests — status code checks, response schema validation, content type assertions — based on the latest response. Compare responses over time: "Has the Create User response changed recently?" — Claude asks Restk to compare the latest response with a previous one for the same request. Restk returns the diff — status code changes, response time differences, header changes, and body structure differences. All values sanitized. Generate and manage entire collections from your terminal: Run /restk:generate_collection_from_code in Claude Code — Claude reads your codebase, detects routes, controllers, and schemas, then creates the full collection in Restk — folders, requests, methods, headers, and body templates. Works with any backend stack — Express, Django, Rails, Spring, NestJS, Laravel, FastAPI, Go, and more. From there, Claude can update requests, add new endpoints, reorganize folders, manage environments — all from your Claude Code console. Analyze performance: "How is the Login endpoint performing?" — Claude asks Restk for performance stats on a specific request. Restk returns mean, median, P95, P99 response times, error rate, and whether performance is trending up or down — across the last 24 hours, 7 days, or 30 days. Detect error patterns: "What errors are happening in my Auth collection?" — Claude asks Restk to scan for error patterns. Restk groups 4xx/5xx errors by status code and URL pattern across a configurable timeframe, and returns sample error messages from the top error groups. Create from scratch: "Create a new collection called 'User Service' with CRUD endpoints for /api/users" — Claude tells Restk to create a collection, add folders, and create individual requests with the right methods, URLs, headers, and body templates. You see it all appear in the app instantly. Full AI audit trail Full AI audit trail Every single interaction is logged. Restk has a dedicated AI Audit tab that shows: Every tool call Claude made Timestamps and duration Success/failure status Total sanitization count — how many values were redacted You get 100% visibility into what AI did with your workspace. Not just trust — verification. Setup: 30 seconds For Claude Code: claude mcp add --transport stdio --scope user restk -- "/Applications/Restk.app/Contents/Resources/restk-bridge" For Claude Desktop: Open Restk settings → click Setup → done. You can connect multiple sessions simultaneously — 3 Claude Code terminals + Cursor, all talking to the same workspace. I do this daily. Built native because developers deserve better Restk is built with native macOS technologies, not Electron. No

Built an open-source API client with Claude Code - ApiArk

I've been building ApiArk - a local-first, open-source API client built with Tauri v2 (Rust + React). Free forever, no login, no cloud. Claude Code helped throughout the entire development process - from architecting the Rust backend, writing React components. What it does: REST, GraphQL, gRPC, WebSocket, SSE, MQTT support Collections stored as plain YAML files - git-friendly Built-in AI assistant (bring your own API key) Import from Postman, Insomnia, Bruno in one click 800+ GitHub stars in 10 days organically. Free to try: https://apiark.dev GitHub: https://github.com/berbicanes/apiark submitted by /u/ScarImaginary9075 [link] [comments]