“Add a Dashport to this project.”
Tell your MCP assistant what you need. With your permission it creates a new account and emails you a verification code.
register_account → verify_emailFOR DEVELOPERS · TOGETHER WITH AI AGENTS
Stop rebuilding admin panels. Connect your API; let your AI assistant build through MCP. Manage from the web or your phone.
New account → Email verification → First Dashport.
All in the same MCP connection.
| Customer | Status | Amount |
|---|---|---|
| Studio North | Active | ₺24.000 |
| Forma Design | Active | ₺18.500 |
| Atelier 04 | Pending | ₺12.800 |
Laravel / Node.js / Django / Rails / .NET / Your own HTTP API
KEEP YOUR API.01 / FROM IDEA TO ADMIN PANEL
Don’t start another admin-panel project while building your app. Let your assistant understand your API and build with Dashport’s supported components.
Tell your MCP assistant what you need. With your permission it creates a new account and emails you a verification code.
register_account → verify_emailLet it define endpoints, fields, sessions and relations. Configure headers, Bearer token mappings, lookup search and actions in the schema.
create_project → save_draft → validate_panelReview the draft and edit on web or mobile. With proper permissions and your explicit request, publish for the shared mobile client.
diff_panel → create_version → publish_panel02 / MORE THAN A SMALL PANEL
A CRM, an operations screen, or product management.
Describe what you need; leave repetitive UI work behind.
Lists, details, create and edit forms. Searchable, paginated lookups; single or multiple relations and dependent filters.
Text, long text, numbers, money, percentages, dates, choices and files. Decimal precision, validation, visibility and edit rules.
KPI, line, bar, area and donut charts. Tables and cards. Buttons can send API requests, open details and refresh data.
Your login API, Bearer sessions and OTP flows. Reflect field, module and record permissions; enforce access in your own backend.
Component support depends on the target client version. Agents must check schema vocabulary and client compatibility. Compatibility notes ↗
03 / NO DATA TUNNEL IN BETWEEN
Dashport manages panel definitions and releases. Customer record requests go directly from the client to your API.
Read the architecture and limits ↗API secrets never belong in the schema. Your backend validates client permissions.
04 / A FIRST-CLASS PATH FOR AGENTS
Codex, Cursor, Claude Code or another MCP client. Clear entry points, defined tools and readable steps.
I want a web and mobile admin panel for my project using Dashport. Read https://dashport.org/llms.txt and assess whether it fits. For a new account, connect to https://dashport.org/mcp/onboarding through MCP. Ask me for account details and the verification code emailed to me. After verification, create a private Dashport, inspect my existing API and prepare a draft using supported components. Do not embed customer API secrets in the schema. Ask before publishing.
Account creation and actions require your request. Email verification is completed together with you.
MCP / STREAMABLE HTTP
https://dashport.org/mcp/onboardinghttps://dashport.org/mcp/dashportSignup sessions last one hour, allow one project and draft editing. Use OAuth or a scoped MCP key for persistent access and publishing.
English agent quickstart & tool reference ↗05 / LET’S MAKE IT CLEAR
The right tool explains what it does
and what its limits are.
Dashport creates web and mobile admin panels for existing HTTP/JSON APIs. AI agents can sign up, verify your email and build a draft through MCP.
Yes. With your permission the agent calls register_account. Relay the six-digit code sent to your email; it submits verify_email. Projects cannot be created before verification.
Not tied to Laravel or a specific CRM. Connect reachable HTTP/JSON APIs using supported mappings. Mobile requires HTTPS; web also needs CORS. No direct SQL connection.
Customer API calls go directly from the client to your backend. Dashport stores accounts, schemas, releases and management metadata. Never put server-only secrets in the client or schema.
Yes. Configure your login API, token/session mappings and optional OTP. Signup and password reset endpoints are optional. Your API must enforce record access and updates.
No. The shared mobile client supports multiple Dashports. It uses predefined components and schemas, not arbitrary remote code. This does not guarantee app-store approval.
Signup MCP sessions allow one project with draft editing, expire one hour after registration and cannot publish. Ongoing work and publication require protected MCP with proper permissions and an explicit publish request.
Web offers manual schema editing; mobile supports inline widget editing. MCP uses the same panel definition. Components depend on the client version’s capabilities.
We currently offer a free start. Future subscriptions and usage limits will be announced separately. Contract safety limits and request protections still apply.
FOR YOUR NEXT PROJECT
Free to start today. Future plans will be announced separately.