Discussion on any other Project Idea for GSoC 2026

[animator]

Please feel free to discuss your ideas/research below.

Like ideas:

• Feature Request: Add MCP Integration Support #1179

[Sandy-07-coder]

I have an idea to improve the user experience in the request body for JSON, #1232

[animator]

Sorry. This does not qualify as an idea as it should be a project which requires a minimum 90 hrs of effort.

[animator]

@IshwariShinde8772 This is not a new project idea, but part of the existing project idea 3. Git Support, UI Workflow Builder & Collection Dashboard

[IshwariShinde8772]

@animator ,Thank you for pointing that out — I completely missed that this was already covered under Project Idea 3. After re-reading the description and related issues, I understand that this fits directly into the Visual Workflow Builder component. The node-based canvas concept and visual execution simulation would align well with that idea, and storing workflows as JSON would naturally support the Git integration requirement. I’ll focus fully on Idea 3 moving forward and align my approach with the existing codebase.

[ExeWall]

Hi everyone!

I'm interested in working on the API Explorer project for GSoC 2026 and I've been exploring the idea in more detail.

From my understanding, the goal is to build an automated pipeline that can:

1. Parse OpenAPI specifications or HTML API documentation
2. Extract endpoints, authentication methods, payload structures, and responses
3. Automatically categorize APIs (AI, finance, weather, etc.)
4. Generate ready-to-use request templates for API Dash users

I had a few questions regarding the implementation:

1. For parsing documentation, should the pipeline primarily focus on OpenAPI specs (JSON/YAML), or should it also support scraping structured HTML documentation?
2. For auto-tagging APIs into categories, would you prefer a rule-based approach (keywords/tags from the spec) or would experimenting with lightweight ML/NLP classification be acceptable?
3. For community contributions, would the preferred approach be a GitHub-based submission workflow (PRs adding new APIs) that is validated automatically by the pipeline?

I’m also considering designing the system with a modular architecture:

• Parser layer (OpenAPI / HTML)
• Metadata extractor
• Categorization engine
• Template generator
• Validation pipeline for community-submitted APIs

Would this align with the expected scope of the project?

Thanks! I'm excited about the possibility of contributing to API Dash.

[animator]

@ExeWall Please follow the application guide and send proposal doc PR for your proposed solution.

[Awaisranahmad]

Hi @animator, I have submitted the PR for my GSoC 2026 application regarding the Multimodal AI & Agent Evaluation Framework. I have integrated my past experience with ilastik (Issue #2581) and AI projects into the proposal. Looking forward to your review!

PR Link: https://github.com/foss42/apidash/pull/1461
GitHub Handle: @Awaisranahmad

[milanprajapati571]

Hey Everyone,
Hello @animator Sir

Hello,

I have been studying the API Explorer idea and the related issue (#619), and I find this project very interesting because it combines automation, OpenAPI parsing, backend pipeline design, and frontend integration to improve the API user experience in API Dash.

Understanding of the problem

As I understand, currently, users need to manually configure API requests before testing them in the workspace, which increases onboarding time and makes it harder to explore new APIs. The goal of this project is to create a curated API library that lets users browse, search, and directly import ready-to-use API templates into their workspace.

This requires building an automation pipeline that can parse OpenAPI / HTML API documentation, categorise APIs, enrich metadata, and generate reusable request templates.

My proposed approach

I am thinking of implementing this feature as a backend automation pipeline with the following stages:

1. API Source Collection

   • Fetch public OpenAPI / Swagger / HTML API docs from known sources
   • Support JSON / YAML / HTML parsing

2. Parsing Layer

   • Parse specs using Python tools (OpenAPI parsers / custom parser)
   • Extract endpoints, methods, headers, auth, payload schema, responses

3. Auto Categorization

   • Tag APIs into categories (AI, Finance, Weather, Social, etc.)
   • Rule-based tagging + keyword matching
   • Design in a way that ML/NLP tagging can be added later

4. Data Enrichment

   • Normalize metadata
   • Add description, tags, auth type, base URL, examples
   • Store in structured format

5. Template Generator

   • Create pre-configured request templates
   • Include endpoint, method, headers, auth placeholders, payload, response

6. Backend Service

   • Node.js / TypeScript API to serve API library
   • Search / filter / category endpoints
   • Template import endpoint

7. Frontend Integration

   • React UI for API Explorer
   • Browse categories
   • Search APIs
   • Import to workspace

8. Community Contribution Support

   • Allow API definitions via GitHub
   • Validate via automation pipeline
   • Keep library up-to-date

9. User Ratings / Reviews

   • Store ratings
   • Show popularity
   • Improve discovery

Technical stack I plan to use

• Python → automation & parsing pipeline
• OpenAPI / Swagger tools → spec parsing
• Node.js / TypeScript → backend service
• React → UI integration
• Database → API metadata storage
• GitHub Actions → validation automation
• Rule-based / NLP tagging → categorisation

Future scope

This system can later support:

• Automatic API updates
• Version tracking
• External API hub integration
• Community-maintained API registry

Clarification

I would like to confirm whether I am on the right track with this understanding and approach.
If possible, please suggest the best path to start working on this issue and any files, documentation, or additional resources I should review to gain a deeper understanding of the current codebase and the expected implementation.

I am very interested in contributing to this feature and would like to start working on related components to better understand the problem in detail and align my implementation with the project goals.

Thank you.

[AB527]

Hey @animator, does a cross device sync feature between desktop and mobile without using a server qualify as a valid idea, more details here #1550

[AkshatRaj00]

Hi, I am interested in working on API Explorer for GSoC 2026…

[isyedrayan1]

Project idea: [GSoC 2026 Idea] Unified Web Hub: Interactive Docs & Agentic Playground

Description:

Problem: > API Dash’s documentation currently lives on GitHub, limiting discovery and navigation. Furthermore, testing new Agentic/MCP features currently requires a local installation.

Proposed Solution:
I propose building a Unified Web Hub to act as the home for the API Dash ecosystem. This includes:

Modern Docs Site: A searchable, beautiful documentation platform (React/TS).

Web Playground: A browser-based interface for Idea #4 (Agentic Testing) where users can witness "Self-Healing" logic in action.

MCP Integration: An online gateway for exploring Model Context Protocol tools.

Impact: > This expands the project from a "tool" to an "ecosystem," significantly lowering the barrier to entry for new developers.

Excited to contribute...

[isyedrayan1]

@animator
would like an quick suggetion and review so that i can submit the proposal on this new idea or based on your ideas #1547

[animator]

@isyedrayan1 go through this resource to study if MCP Apps can be served via API Dash MCP server.