All organizations · GSoC 2026 · Programming languages, Infrastructure and cloud
MetaCall
Simplifying the embedding of programming languages
When working with different technologies and developers of different programming languages, the productivity of the entire team worsens due to the lack of interoperability and communication between them. If the developers need two technologies which are written in different programming languages, for instance, a C/C++ library called from NodeJS, the team usually needs to port to one of the two languages or write a wrapper around them. Maintaining a port of a library or the plumbing code is frequently error-prone, time-consuming, and does not add any value to the final product. The main objective of MetaCall is to provide a transparent interoperability in both ways, no matter what language you are using, so you feel like you are using a library written in the same language but in fact, it may be written in C, NodeJS or any other language. MetaCall currently provides a mechanism to introspect the types and function signatures, which allows us to provide this type info to the caller language. You can have type safety and at the same time avoid boilerplate in both directions. It addresses the main shortcomings of embedding independent languages separately. Having a common …
- python
- c++
- rust
- nodejs
- docker
- cloud
- polyglot
- faas
- languages
- ffi
Project ideas
17 ideas on its 2026 ideas page; of the 16 that state a difficulty: 12 medium, 4 hard. Sizes: 9 small, 6 medium, 2 large. 10 mentors named.
- Implement Multi-Language Parser medium medium
- Function Mesh Implementation large hard
- Code Coverage and Memory Tracking Improvements small hard
- MetaCall Deploy and MetaCall FaaS Completion small medium
- MetaCall SSR (Server-Side Rendering) Server large medium
- Rust Loader Update medium hard
- Implement Core C Support for CI & Distributables medium medium
- Implement Model Context Protocol (MCP) Support for MetaCall Deploy & FaaS medium medium
- Extended Platform and Architecture Support for MetaCall medium medium
- Zig Port Implementation small medium
- Modernize C# (.NET Core) Loader: Class Support, Pure Functions, and Type Expansion small medium
- Redesign MetaCall Dashboard for MetaCall FaaS medium
- MetaSSR CI/CD & Docs Improvements small medium
- Fuzzing Engine for MetaCall Testing Center small medium
- Direct metacall/core C API Model Context Protocol (MCP) Server small medium
- Metacircular Self-Registration of MetaCall API small hard
- MetaSSR as High-Performance Rust Worker Node for MetaCall Function Mesh small medium
Read the ideas page. Ideas are for scope reference; never copy one into a proposal.
History
In GSoC since 2021, 5 years. Projects per year: '21: 3, '22: 5, '23: 4, '24: 7, '26: 6.
On GitHub
27 repositories pushed to in the last year. Main languages: TypeScript (6), Shell (4), JavaScript (3), Python (3), Rust (3), C (2).
Links and channels
- Website: https://metacall.io
- Ideas page: https://github.com/metacall/gsoc-2026
- Contributor guide: https://github.com/metacall/gsoc-2026
- Source code: https://github.com/metacall
- Email: contact@metacall.io
- Chat: https://discord.gg/upwP4mwJWa
- Chat: https://t.me/joinchat/BMSVbBatp0Vi4s5l4VgUgg
- Chat: https://matrix.to/#/#metacall:matrix.org
git-into-gsoc org "MetaCall" --shortlist
git-into-gsoc repos "MetaCall"
git-into-gsoc issues --org "MetaCall"
or ask your assistant: "Which MetaCall repositories merge newcomers' pull requests, and which beginner issues are still free?"
Those commands read live data: which repositories merge outside pull requests, and which beginner issues nobody has claimed. Install in two minutes.